Thanks. Looks like that will work great!
On Tue, 24 Apr 2012, Bill Hoffman wrote:
> On 4/24/2012 12:07 PM, Leif Walsh wrote:
> > Also, it would be nice if there was a way to specify that only some of
> > the commands should be run with valgrind, but that may be asking too
> > much.
> >
>
> Wha
On 4/24/2012 12:07 PM, Leif Walsh wrote:
Also, it would be nice if there was a way to specify that only some of
the commands should be run with valgrind, but that may be asking too
much.
What I usually do is use the --trace-children option. I have even
patched (accepted upstream now), valgri
Also, it would be nice if there was a way to specify that only some of
the commands should be run with valgrind, but that may be asking too
much.
On Tue, 24 Apr 2012, Leif Walsh wrote:
> Hi,
>
> I have some tests that need to be run as distinct commands, for example:
>
> foo_test --crash
> test
Hi,
I have some tests that need to be run as distinct commands, for example:
foo_test --crash
test "$?" != "0"
foo_test --recover
Right now, I have shell scripts that do this, so I have something like
add_test(foo_test run_foo_test.sh ${CMAKE_CFG_INTDIR}/foo_test)
but this doesn't work with Me
