Wireshark-dev: Re: [Wireshark-dev] Volatile Read of Wireshark Frames
From: "FIXED-TERM Scholz Tobias (DC-IA/EAM6)" <[email protected]>
Date: Thu, 26 Feb 2015 10:55:27 +0000
I've mistaked the flags. I first thought, that those 'visited' flags won't be resetted for the case of starting a new capture. That's why I asked, if it is possible to reset those flags to FALSE.

But now, since I understand the conduct of those flags, my dissector works fine.

Thanks for your help!




-----Urspr√ľngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] Im Auftrag von Jeff Morriss
Gesendet: Mittwoch, 25. Februar 2015 21:50
An: Developer support list for Wireshark
Betreff: Re: [Wireshark-dev] Volatile Read of Wireshark Frames

On 02/25/15 09:14, FIXED-TERM Scholz Tobias (DC-IA/EAM6) wrote:
> Thanks for the hint with "pinfo->fd->flags.visited". This will help me
> to improve my code.
>
> I implemented this variable to my dissector and watched the conduct of
> it. It reveals, that those flags, will not be reset (to FALSE), if I'm
> starting a new capture without booting Wireshark.
>
> Is it possible to reset all those visited-flags of frames, which have
> already been dissected in the first capture, so that starting with a new
> capture the flags are all FALSE?

I'm not sure I follow.  If you start a new capture or open a new file 
then all of the previously-dissected frames go away: they cease to 
exist.  The new frames will, of course, have 'visited' set to FALSE the 
first time your dissector sees them.

Your dissector can register an initialization routine (with 
register_init_routine()) if it wants to clean up before a new file is 
dissected (amongst other uses).

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