Wireshark-dev: Re: [Wireshark-dev] g_mem-chunk_destroy does not free memory for GLib > 2.8
From: Jeff Morriss <[email protected]>
Date: Tue, 20 Oct 2009 16:19:24 -0400
Bill Meier wrote:
Jeff Morriss wrote:
Bill Meier wrote:
   I've found at least one case wherein se_alloc'd memory
   is referenced after it's been freed. (I think this case just happens
   to work because the memory wasn't yet reassigned).
I was contemplating adding an optional memory-scrubber to ensure that we're not doing that: just writing 0xdeadbeef to the ep_ and se_ alloc'd memory when we free it.
I was thinking the same thing ....
I fixed a few cases of this and I'm not getting any more failures with 
the sample captures I have.  Is the case you found fixed?
If so, should we turn on memory scrubbing while fuzz testing?