|
|
Log in / Subscribe / Register

Clarification

Clarification

Posted Jan 15, 2009 15:51 UTC (Thu) by pr1268 (guest, #24648)
In reply to: The Valgrind Project releases version 3.4.0 by pr1268
Parent article: The Valgrind Project releases version 3.4.0

I should clarify that Valgrind says that the above program possibly lost 19 bytes. And, the Valgrind documentation mentions the possibility of false positives related to what this program does.

Still, I find it interesting to analyze the behavior of C++ allocator-based container and "almost container" classes using Valgrind. Not to mention its usefulness in finding uninitialized memory issues as discussed below.


to post comments

Clarification

Posted Jan 15, 2009 16:59 UTC (Thu) by jengelh (subscriber, #33263) [Link] (1 responses)

>possibly lost 19 bytes.

And let's not forget that glibc and libdl always keep some memory unfreed. Even more so, I get "use of uninitialized value" from libdl :-/

Clarification

Posted Jan 24, 2009 11:22 UTC (Sat) by oak (guest, #2786) [Link]

Valgrind has suppressions for lots of error messages from libdl, but for
suppressions to work it needs debug symbols for libdl, do you have those?
(AFAIK most distros don't strip libdl debug symbols from libc6 package)


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds