On Mon, Feb 25, 2008 at 10:31 PM, Nicholas Nethercote <[EMAIL PROTECTED]> wrote: > For this specific problem, it would be easier to use a filter script for the > test output, to remove the information you don't want. See the comment at > the top of tests/vg_regtest, particular the stuff about > "stderr_filter"/"stdout_filter".
Thanks for the hint, by this time I have specified a custom stderr filter for some of the tests. By the way, does the patch below make sense or is the comment in tests/vg_regtest.in correct as it is now ? Index: tests/vg_regtest.in =================================================================== --- tests/vg_regtest.in (revision 7477) +++ tests/vg_regtest.in (working copy) @@ -61,7 +61,7 @@ # Note that filters are necessary for stderr results to filter out things that # always change, eg. process id numbers. # -# Expected stdout (filtered) is kept in <test>.stdout.exp[0-9]* (can be more +# Expected stdout (filtered) is kept in <test>.stdout.exp* (can be more # than one expected output). It can be missing if it would be empty. Expected # stderr (filtered) is kept in <test>.stderr.exp*. There must be at least # one stderr.exp* file. Bart. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
