|
From: Patrick O. <Pat...@in...> - 2004-08-18 14:27:42
|
On Wed, 2004-08-18 at 15:34, Tom Hughes wrote: > In message <1092831252.554.137.camel@debian> > Patrick Ohly <Pat...@in...> wrote: > > > perhaps I am missing something obvious, but > > is there a possibility to print the address > > of a memory block which was leaked in the > > report of the leak? I'm using memcheck. > > Not at the moment. Can you point me in the right direction so that (when I find the time) I can provide a patch which does that? Would that be accepted into valgrind mainline? > > I know that this would be impossible when > > --leak-resolution causes several leaks to > > be merged into one, but in my case there's > > just one block. > > Even --leak-resolution=high will merge blocks allocated in > exactly the same place. Yep, but in my case it really was just one chunk. Sounds like "--leak-resolution=none" would be a good extension, too. -- Best Regards Patrick Ohly Senior Software Engineer Intel GmbH Software & Solutions Group Hermuelheimer Strasse 8a 50321 Bruehl Germany Tel: +49-2232-2090-30 Fax: +49-2232-2090-29 |