Re: [Valgrind-users] at a loss

[Olly B. <ol...@su...>]

On Wed, May 14, 2003 at 08:41:06AM +0100, Nicholas Nethercote wrote:
> But first, just try "valgrind --leak-check=yes <program>", see how that
> works.

On a slightly tangential note, if your program is built using libtool
(as Michael's was, judging by the program name "src/.libs/lt-myapp") then
running the actual binary in .lib may not work.  The most reliable way
to run it under valgrind would be:

libtool --mode=execute valgrind --leak-check=yes src/myapp

This lets libtool take care of any messing around with environmental
variables and the like that is required to get the program to run
before it has been installed.

The only wrinkle is that --mode=execute seems to have problems with
passing arguments to valgrind or the program in libtool 1.4.2 (you can
set VALGRIND_OPTS to pass options to valgrind).  I've had no such
problems with libtool 1.5.

Cheers,
    Olly