Wireshark mailing list archives
Re: Running a function only on first run
From: Graham Bloice <graham.bloice () trihedral com>
Date: Tue, 06 Apr 2010 17:58:26 +0100
On 06/04/2010 17:40, Jeremy O'Brien wrote:
Hello, I'm trying to have Wireshark maintain a list of certain information from packets as it receives them (using a GHashTable or a GSList, not sure which yet). The problem I am facing is that the code in my dissection routine that does this gets run once on each packet as they are analyzed, but also every time I click on a packet. I understand this is how Wireshark works, but I was wondering if there was some way of telling if this is a "first run" analysis or a second-visiting of the same packet, without maintaining my own variables to keep track of this for each packet. Does this make sense?
Try PINFO_FD_VISITED(pinfo) on the pinfo you have. Visited gets set after the first pass. -- Regards, Graham Bloice
___________________________________________________________________________ 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
Current thread:
- Running a function only on first run Jeremy O'Brien (Apr 06)
- Re: Running a function only on first run Graham Bloice (Apr 06)
- Re: Running a function only on first run Jeremy O'Brien (Apr 06)
- Re: Running a function only on first run Maynard, Chris (Apr 06)
- Re: Running a function only on first run Jeremy O'Brien (Apr 07)
- Re: Running a function only on first run Anders Broman (Apr 07)
- Re: Running a function only on first run Anders Broman (Apr 07)
- Re: Running a function only on first run Jeff Morriss (Apr 07)
- Re: Running a function only on first run Jeremy O'Brien (Apr 06)
- Re: Running a function only on first run Graham Bloice (Apr 06)