Wireshark mailing list archives

Re: g_mem-chunk_destroy does not free memory for GLib > 2.8


From: Jeff Morriss <jeff.morriss.ws () gmail com>
Date: Thu, 15 Oct 2009 17:49:22 -0400

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.

Maybe I should wait 'til this is fixed.
___________________________________________________________________________
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: