Re: [Valgrind-users] Leak detection during program execution

[Nicholas N. <nj...@ca...>]

On 26 May 2003, Stephane Donze wrote:

> HP's Tru64 Unix has a tool that is very similar to valgrind. It's called
> Third Degree (see
> http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V40F_HTML/APS30ETE/THRDDGRC.HTM#third-custom-sec ) and has a very nice feature allowing to track memory leaks during program execution. In the .third configuration script you can put a directive triggering the leak detection after a specific function has been called. For instance, if your .third config file contains the following line
>
> new leaks after MyPeriodicFunction every 2
>
> the instrumented program will perform a leak detection every 2 calls to
> MyPeriodicFunction, thus detecting only "real" memory leaks (i.e. the
> memory leaks created by all the code executed between two calls to
> MyPeriodicFunction). See the complete documentation of the .third
> features at
> http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V40F_HTML/MAN/MAN5/0125____.HTM
>
> Do you think it feasible to add those features to valgrind ?

Valgrind allows leak checks to be done at arbitrary times by inserting the
VALGRIND_DO_LEAK_CHECK macro into your program.  The disadvantage is that
it does require re-compiling your program.  The advantage is that the
feature is already there :)  Does this suit your needs?

N