
5 Jan
2009
5 Jan
'09
11 p.m.
On Sun, Jan 04, 2009 at 06:05:00PM -0800, Bill Fenner wrote:
Any ideas where to look to find out what is freeing this node? (I tried --enable-dmalloc but the dmalloc linkage didn't work)
I fixed the dmalloc linkage so that it works with newer versions of dmalloc. But unfortunately, dmalloc stays silent (but I admit not being a dmalloc expert). Anyway, I have committed the dmalloc linkage fixes.
I went back to revision 7563 (2008-01-01), 6403 (2007-01-01), and 3078 (2006-06-06) and they all show the same problem. If this ever worked, it must have been a long time ago. I guess I will leave this alone for the moment; something is likely overwriting a pointer here and I am not sure how to track this down at the moment...
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany
Fax: +49 421 200 3103 http://www.jacobs-university.de/