As far as I know, there's no way to do that.
Last time I wanted this, I hacked it into my local copy of valgrind
(actually just tracking a single address, and printing out one - even
when multiple copies were leaked). Unfortunately, I've since lost that
patch. Fortunately, it was really simple - s
Hi all,
I am trying to find a well-hidden memory leak. To do so, it would be
immensely useful to know the memory addresses of the leaked objects.
Is there any way I can tell valgrind to show the addresses in its
memory leak output (just like it does e.g. on access violations)?
Thanks,
Rainer
---
