Wireshark-dev: Re: [Wireshark-dev] File-scope memory on subsequent passes
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Pascal Quantin <pascal.quantin@xxxxxxxxx>
Date: Mon, 30 Sep 2013 19:10:29 +0200
2013/9/30 Evan Huus <eapache@xxxxxxxxx>
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.