Re: [Valgrind-users] debugging gtk-related memory leaks

[Julian Seward <jseward acm org>]

> Maybe you should set G_SLICE=always-malloc in the environment in order
> to make valgrind more useful:
>
>   http://developer.gnome.org/doc/API/2.0/glib/glib-running.html

I agree; from a guess I'd say that glib is using a private allocator, 
which confuses the issue.

Unrelatedly ..

It looks like the 'valgrind-3.1.1-Debian' you are using has been
shipped without a set of suppressions suitable for getting rid of
all the complaints of the form

==3722== Conditional jump or move depends on uninitialised value(s)
==3722==    at 0x401139F: (within /lib/ld-2.3.6.so)
==3722==    by 0x4006ACE: (within /lib/ld-2.3.6.so)
==3722==    by 0x48A14AF: (within /lib/tls/i686/cmov/libc-2.3.6.so)
==3722==    by 0x400BA5E: (within /lib/ld-2.3.6.so)

which is a shame.  It may be that if you install debug info packages
for /lib/ld-2.3.6.so and/or libc-2.3.6.so, that noise will go away.

J