On Mon, 2010-08-23 at 16:32 +0200, Milan Crha wrote: > On Mon, 2010-08-23 at 13:10 +0100, David Woodhouse wrote: > > The fixes I mentioned are sitting in my working tree, and I'll commit > > and push them today.
This is awesome work - thanks ! :-) > > If they're referenced by a global variable, surely valgrind would know > > that they're reachable and would not complain about them? > > I do not know how it works precisely. It should work nicely as David says. > I just got a thought, what if some of those "possibly lost" come from > GSlice? Then G_SLICE=always-malloc should help valgrind with it. At > least a bit. Right - except for this, which is a disaster area :-) I had forgotten that it was critical to turn this on (which turns off the glib slab allocator) before valgrinding myself ;-) Hmm - I wonder how best to deal with that. I wonder if the glib guys would accept a patch that incorporated /usr/include/valgrind.h's RUNNING_ON_VALGRIND magic ;-) [ amazingly fun etc. ]. Thanks, Michael. -- michael.me...@novell.com <><, Pseudo Engineer, itinerant idiot _______________________________________________ evolution-hackers mailing list firstname.lastname@example.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers