On Sun, Dec 5, 2010 at 2:20 AM, Peter Clifton <pc...@cam.ac.uk> wrote: > On Sat, 2010-12-04 at 11:15 +1100, Stephen Ecob wrote: branch.. sorry). [...] > So, a mix of NOT LEAKS, and "might be leaks". We need back-traces of the > cases where callers are allocating things repeatedly and not freeing > them. Because these are showing up in your DMalloc output as being where > memory is allocated (pretty generic routines), we would need a > back-trace to see which code caused the allocation before any could be > fixed.
Thanks for looking those over, your observations are helpful. I'll investigate further today. > I believe valgrind is good at detecting leaks! So I hear. I should take the time to learn it some time :) _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user