tag 353245 + moreinfo thanks On Thu, Feb 16, 2006 at 08:20:28PM -0500, Justin Pryzby wrote: > Package: valgrind > Version: 1:3.1.0-2.1 > Severity: normal > Tags: upstream > > I'm debugging a program with valgrind: > $ valgrind ./usnoquery_main > ... > ==22610== Reachable blocks (those to which a pointer was found) are not > shown. > ==22610== To see them, rerun with: --show-reachable=yes > > So then I ran: > $ valgrind --show-reachable=yes ./usnoquery_main > > but it didn't show me any reachable blocks (but the message to use > show-reachable went away). > > If I also add leak-check=full, then I get the expected backtrace, > revealing that libcurl still has some space allocated. valgrind > should either implicitly enable the necessary leak checks (possibly > with a message to stderr), or stop implying that it will.
You give no way to reproduce the issue which makes it very hard to test if the issue is still here. Could you produce a test-case ? is the issue still here for you? -- ·O· Pierre Habouzit ··O madco...@debian.org OOO http://www.madism.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
