diff options
author | Dan Fandrich <dan@coneharvesters.com> | 2014-02-07 22:15:02 +0100 |
---|---|---|
committer | Dan Fandrich <dan@coneharvesters.com> | 2014-02-07 22:43:34 +0100 |
commit | e2dae8a7c2c417e70262b23d4c1924a43a9d56e1 (patch) | |
tree | 764c71a31cbe77b65e706e4f2f0d9a065bde6f18 | |
parent | a3a6b03c308866be16aa9e2861a434fe45433a91 (diff) |
runtests: Disable valgrind when debugging
This was already mostly being done, except that analysis after the
test still assumed that the valgrind log files would be available. An
alternative way to handle the valgrind + gdb combination could be to
enable one of the valgrind debugger hooks.
-rwxr-xr-x | tests/runtests.pl | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/tests/runtests.pl b/tests/runtests.pl index 44b22d75c..0de76e3d1 100755 --- a/tests/runtests.pl +++ b/tests/runtests.pl @@ -3334,6 +3334,13 @@ sub singletest { $DBGCURL=$CMDLINE; } + if($gdbthis) { + # gdb is incompatible with valgrind, so disable it when debugging + # Perhaps a better approach would be to run it under valgrind anyway + # with --db-attach=yes or --vgdb=yes. + $disablevalgrind=1; + } + if($fail_due_event_based) { logmsg "This test cannot run event based\n"; return -1; |