Wireshark mailing list archives

Re: Dissector being called with tree != NULL in the middle of the capture

From: Guy Harris <guy () alum mit edu>
Date: Tue, 20 Oct 2009 14:38:18 -0700


On Oct 20, 2009, at 11:00 AM, David Aggeler wrote:

Is a dissector supposed to be able to handle something like this, i.e.
being called with tree specified somewhere in the middle of the  
stream?


Yes.  A dissector is expected to be able to handle being called with  
tree null or non-null at any point; it's up to the Wireshark/TShark/ 
etc. core to choose whether it needs, and hence asks for, a protocol  
tree or not.
___________________________________________________________________________
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:

Dissector being called with tree != NULL in the middle of the capture David Aggeler (Oct 20)
- Re: Dissector being called with tree != NULL in the middle of the capture Guy Harris (Oct 20)
  - Re: Dissector being called with tree != NULL in the middle of the capture David Aggeler (Oct 21)