Re: File-scope memory on subsequent passes

[Pascal Quantin <pascal.quantin () gmail com>]

2013/9/30 Evan Huus <eapache () gmail com>

> I recently found that there are some dissectors which allocate
> file-scope memory every time they dissect a packet (not just on the
> first pass, when the packet is unvisited). Can anybody think of a
> reason for this, or should it be considered a bug?
>
> I have attached a trivial (if hacky) patch which adds an assertion if
> file-scope memory is used during the second pass of two-pass tshark.
> Applying this and then running "fuzz-test.sh -2" on the menagerie
> results in many failures.
>
> This is not a proposal or anything, just an idea I had that produced
> some unexpected results. I am curious if this is a valid use or known
> issue or something.

Hi Evan,

right now I cannot think to a valid use case for this, but maybe I'm
missing something.

Regards,
Pascal.

___________________________________________________________________________
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