Wireshark · Wireshark-dev: Re: [Wireshark-dev] Dissector being called with tree != NULL in the middle of the capture

Wireshark-dev: Re: [Wireshark-dev] Dissector being called with tree != NULL in the middle of th

From: Guy Harris <guy@xxxxxxxxxxxx>

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 thestream?

Yes. A dissector is expected to be able to handle being called withtree 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 protocoltree or not.

Follow-Ups:
- Re: [Wireshark-dev] Dissector being called with tree != NULL in the middle of the capture
  - From: David Aggeler

References:
- [Wireshark-dev] Dissector being called with tree != NULL in the middle of the capture
  - From: David Aggeler

Prev by Date: [Wireshark-dev] Dissector being called with tree != NULL in the middle of the capture
Next by Date: Re: [Wireshark-dev] g_mem-chunk_destroy does not free memory for GLib > 2.8
Previous by thread: [Wireshark-dev] Dissector being called with tree != NULL in the middle of the capture
Next by thread: Re: [Wireshark-dev] Dissector being called with tree != NULL in the middle of the capture
Index(es):
- Date
- Thread