[Valgrind-users] at a loss

[Michael L. <in...@pa...>]

I am at a loss as to how to use valgrind.  I have read the manual and a h=
owto. =20
Using this command=20

export GLIBCPP_FORCE_NEW=3D1; valgrind --skin=3Dmemcheck --leak-check=3Dy=
es=20
--show-reachable=3Dyes --logfile=3Ddebug.out --suppressions=3Dxfree-3.sup=
p=20
--suppressions=3Dxfree-4.supp --suppressions=3Ddefault.supp=20
--suppressions=3Dglibc-2.2.supp src/.libs/lt-myapp

My application produces hundreds of lines looking like

=3D=3D26316=3D=3D 216 bytes in 21 blocks are still reachable in loss reco=
rd 77 of 124
=3D=3D26316=3D=3D    at 0x40160989: malloc (in /usr/lib/valgrind/valgrind=
=2Eso)
=3D=3D26316=3D=3D    by 0x40B33B2F: __GI___strdup (in /lib/libc-2.3.1.so)
=3D=3D26316=3D=3D    by 0x40F5C37A: resolve_object (in /usr/X11R6/lib/lib=
X11.so.6.2)
=3D=3D26316=3D=3D    by 0x40F5BF7C: _XlcDynamicLoad (in /usr/X11R6/lib/li=
bX11.so.6.2)
=3D=3D26316=3D=3D=20

What do I do with this stuff?  It looks like it comes from an X11 library=
 but=20
the command line includes suppressions for X11.  Why isn't X11 output=20
suppressed?  Where do I get a suppressions file for Qt?

Thanks.

-- Michael