|
From: Tom H. <to...@co...> - 2005-08-26 07:55:53
|
In message <6.1.2.0.0.20050826094230.02b81878@192.168.5.6>
Dennis Lubert <pla...@in...> wrote:
> Btw, to all others in the list, can I somehow print the address of the
> memory still reachable/leaked ? It would help to track it down when
> writing memory addresses of various internal stuff..
No, because valgrind doesn't remember that when it is searching for
leaks because it wants to aggregate leaks together - each leak report
may correspond to a number of blocks so there is no one block whose
address could be printed.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|