On Mon, Feb 18, 2013 at 9:58 PM, Diego Biurrun <[email protected]> wrote: > On Mon, Feb 18, 2013 at 09:04:26PM +0100, Reinhard Tartler wrote: >> With this configure option, "make fate" executes all programs with >> valgrind. This option optionally takes as parameter the complete path >> and command line for invoking the valgrind program. For use in the FATE >> environment, use "./configure --valgrind='valgrind --error-exitcode=1'" > > Why do I still have to pass an extra parameter to valgrind manually?
You don't, ./configure --valgrind just works. However, if you want to execute valgrind with the option --error-exitcode=1, as currently done on some of our fate instances, you can optionally pass them as arguments. > >> Patch based on work by: Reimar Doeffinger <[email protected]> > > Döffinger > >> --- a/configure >> +++ b/configure >> @@ -278,6 +278,10 @@ Developer options (useful when working on Libav itself): >> --enable-debug=LEVEL set the debug level [$debuglevel] >> --disable-optimizations disable compiler optimizations >> --enable-extra-warnings enable more compiler warnings >> + --valgrind=VALGRIND run "make fate" tests through valgrind to detect >> memory > > "make fate" --> FATE I don't think that this change will make the situation any clearer, so I'd prefer to keep it as it is. But I wouldn't insist on the current wording either, so I'm unsure what to do right now. -- regards, Reinhard _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
