Re: [Valgrind-users] Memcheck and lost pointer tracking

[Theodoros V. K. <th...@gm...>]

On Fri, 8 May 2009, Nicholas Nethercote wrote:

> This paper is related too:
>
>    author      = {Jonas Maebe and Michiel Ronsse and Koen De Bosschere},
>    title       = {Precise detection of memory leaks},
>    booktitle   = {Proceedings of the Second International Workshop on Dynamic
>                   Analysis (WODA 2004)},
>    pages       = {},
>    address     = {Edinburgh, Scotland},
>    month       = may,
>    year        = 2004,

I'll have a look at it.

> In general, what you are proposing is possible, but it's not easy, is
> really slow and would be lots of extra code in Memcheck.

What if it was done in two passes? Run memcheck normally, and then re-run 
valgrind repeatedly in order to track a specific memory leak each time. 
You could say e.g. --tool=analyse-leak --with-alloc=foo.c:111 and have 
valgrind track those pointers only. Could we exploit that to make things 
easier speed-wise and coding-wise?

IMO when you _know_ you have a problem, a slower but effective valgrind is 
definitely acceptable.


Cheers,

Theodoros