http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2017
------- Comment #7 from stephentfisher@xxxxxxxxx 2007-12-02 21:24 GMT -------
Thanks for your updates! Especially the way to reproduce the bug with fewer
steps :).
I've been unsuccessful in tracking down the problem with many memory debuggers
on MacOS X and Linux (OS X: libMallocDebug, libgmalloc, MallocDebug, Duma
Linux: Valgrind, MALLOC_CHECK_ env var, Electric Fence, Duma). I CAN now catch
the problem when running a memory debugger on OS X set to force a crash on the
bad g_free, but it doesn't crash in OS X otherwise. What makes it hard for
some of the OS X debuggers is that the problem doesn't happen every time when
you go into the VoIP stats dialog so it takes too long to debug/machine runs
out of resources putting guard pages and such in.
According to one of the debuggers in OS X, the g_free of the src_addr.data is
what actually corrupted the heap. Gibc on Linux catches a suspected double
free in the same place.
Now I'm resorting to putting g_warning() (like printf) to display values of
variables and pointers at various parts of voip_calls.c.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
