Re: Problem in using a global variable in wireshark/gtk folder which is defined in epan/dissectors/ folder

[Vishnu Bhatt <vishnu.bhatt () aricent com>]

<<Make sure GTK+ is linked to the same code as the dissectors.>>
Thanks for the reply. How can I check whether GTK+ is linked to the same code as dissectors. Can you please elaborate 
it a little bit. I think the problem is somewhere in linking GTK code with the dissector code.

Regards
Vishnu Bhatt

-----Original Message-----
From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Stephen Fisher
Sent: Wednesday, May 02, 2012 11:14 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Problem in using a global variable in wireshark/gtk folder which is defined in 
epan/dissectors/ folder


---- On Wed, 02 May 2012 02:01:02 -0600 Vishnu Bhatt  wrote ----

> I am implementing a functionality where I want to scan all packets in a pcap file, and depending on a configuration, 
> select only the relevant packets of a call flow (basically create a filter and then apply it). I will be using only 
> the GUI mode (no tshark). Tap interface will not serve my purpose.

In what way does the tap not work?

> Is there a quick fix way to call UI code from the dissectors code? I simply want to prototype and test.

Make sure GTK+ is linked to the same code as the dissectors.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe