|
From: Jo J. <joj...@ho...> - 2004-11-30 21:14:13
|
I'm using valgrind with leak checking on a daemon, but I'm getting a ton of
reports of libc leaks. I've read the docs in detail on suppressing reports,
but I can't find anything on suppressing these leak reports. Can someone
tell me how to suppress reports such as this:
==3297== 28 bytes in 1 blocks are still reachable in loss record 1 of 3
==3297== at 0x1B902A90: malloc (vg_replace_malloc.c:131)
==3297== by 0x1B8EEB64: _dl_map_object_deps (in /lib/ld-2.3.3.so)
==3297== by 0x4AD37863: dl_open_worker (in /lib/tls/libc-2.3.3.so)
==3297== by 0x1B8EFB65: _dl_catch_error (in /lib/ld-2.3.3.so)
I suspect I can fix all the other "still reachable" reports when I've got
this one down.
This is my call to valgrind:
valgrind --trace-children=yes --tool=memcheck --log-file=valerror.txt \
--suppressions=suppression.supp --leak-check=yes \
--show-reachable=yes ./mydaemon
_________________________________________________________________
Don't just Search. Find! http://search.sympatico.msn.ca/default.aspx The new
MSN Search! Check it out!
|