Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] Issues with creation of new thread

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Fri, 1 May 2009 09:23:37 -0700


On May 1, 2009, at 5:04 AM, harsha gampa wrote:

In wireshark , gtk/main.c code , ther's a call to gtk_main() where the main thread control is given to gtk.

I need to automate a particular user interaction i.e. select the RTP/Stream Analysis ... from menu .

For that i have written a small code as follows :
Just before the call to gtk_main() , i have created a thread

Don't do that. There is no guarantee that you can safely do that, as you've discovered; you're running into errors that are, I suspect, caused by the GTK+ event loop running in parallel in more than one thread (one of which says so explicitly).

  • References:
    • [Wireshark-dev] Issues with creation of new thread
      • From: harsha gampa
  • Prev by Date: Re: [Wireshark-dev] new plug-in dissector - no packets, displayed when dissector specific filter applied
  • Next by Date: [Wireshark-dev] make error: gcc
  • Previous by thread: [Wireshark-dev] Issues with creation of new thread
  • Next by thread: Re: [Wireshark-dev] new plug-in dissector - no packets, displayed when dissector specific filter applied
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation