Darryl Miles <[EMAIL PROTECTED]> writes:
> John Shilkaitis wrote:
> > On Fri, Oct 24, 2008 at 4:58 PM, Darryl Miles 
> >     Is it possible to make valgrind dump out the locations of the "Still
> >     Reachable" pointers to still allocated memory at program exit ?
> > 
> > Add --show-reachable=yes to your command line options.
> 
> Sorry I was not clear.  I am aware of the --show-reachable=yes.
[snip]
> But it doesn't show me:
>   * Where in memory they are reachable from (the address of one of more 
> pointers, pointing to/into the block).  This is the magic thing that 
> makes them "Still Reachable" as opposed to "Lost".
>   * The address of each block itself (this data appears collapsed by the 
> reporting of the number of similar allocations).

Have you tried show reachable with --leak-resolution=high?  The
default is `low'.

Supposedly on the trunk there is an option for providing better leak
error information which might be more helpful. ``--track-origins''.
I'm just regurgitating information, haven't tried it myself, YMMV, etc.
etc.

-tom

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to