From: Dan Fandrich <dan@coneharvesters.com>
Date: Fri, 7 Feb 2014 21:15:02 +0000 (+0100)
Subject: runtests: Disable valgrind when debugging
X-Git-Tag: curl-7_36_0~193
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=e2dae8a7c2c417e70262b23d4c1924a43a9d56e1;p=thirdparty%2Fcurl.git

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.
---

diff --git a/tests/runtests.pl b/tests/runtests.pl
index 44b22d75cf..0de76e3d1d 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;