|
From: Christian P. <tr...@ge...> - 2005-08-26 11:17:30
|
On Friday 26 August 2005 09:50, Dennis Lubert 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 writi= ng > memory addresses of various internal stuff.. Also very helpful would be a dump of those memory blocks to be reviewed in = a=20 special output file (in what format ever). Bewides, is it possible to generate a memory dump of an application that is= =20 currently running W/O valgrind atop? Because I don't seem to reproduce the real bad leaks, but the daemon leaks= =20 within a run of about 15 hours about 500MB that doesn't get freed. I would like to be able to dump them into a file (just like the coredump, b= ut=20 w/o crashing), and review them with a hex-editor (for example). Thanks in advance, Christian Parpart. |