Michal Marek fixed the test script to be able to use valgrind even when the

lib is built shared with libtool.

CHANGES

@@ -7,6 +7,9 @@
                                   Changelog
 
 Daniel S (25 October 2007)
+- Michal Marek fixed the test script to be able to use valgrind even when the
+  lib is built shared with libtool.
+
 - Fixed a few memory leaks when the same easy handle is re-used to request
   URLs with different protocols. FTP and TFTP related leaks. Caught thanks to
   Dan F's new test cases.

RELEASE-NOTES

@@ -44,6 +44,7 @@ This release includes the following bugfixes:
  o re-used connections a bit too much when using non-SSL protocols tunneled
    over a HTTP proxy
  o embed the manifest in VC8 builds
+ o use valgrind in the tests even when the lib is built shared with libtool
 
 This release includes the following known bugs:
 

tests/runtests.pl

@@ -1747,7 +1747,7 @@ sub singletest {
     }
 
     if($valgrind) {
-        $CMDLINE = "valgrind ".$valgrind_tool."--leak-check=yes --num-callers=16 ${valgrind_logfile}=log/valgrind$testnum $CMDLINE";
+        $CMDLINE = "$valgrind ".$valgrind_tool."--leak-check=yes --num-callers=16 ${valgrind_logfile}=log/valgrind$testnum $CMDLINE";
     }
 
     $CMDLINE .= "$cmdargs >>$STDOUT 2>>$STDERR";
@@ -2537,10 +2537,8 @@ if($valgrind) {
 	open(C, "<$CURL");
 	my $l = <C>;
 	if($l =~ /^\#\!/) {
-	    # The first line starts with "#!" which implies a shell-script.
-	    # This means libcurl is built shared and curl is a wrapper-script
-	    # Disable valgrind in this setup
-	    $valgrind=0;
+	    # A shell script. This is typically when built with libtool,
+	    $valgrind="../libtool --mode=execute $valgrind";
 	}
 	close(C);