From: brarcher <brarcher@64e312b2-a51f-0410-8e61-82d0ca0eb02a>
Date: Thu, 19 Dec 2013 16:27:53 +0000 (+0000)
Subject: test_mem_leaks.sh: use libtool to invoke check_mem_leaks
X-Git-Tag: 0.10.0~305
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c7a5ffdc66d975a24073a6fd1a9266344725c759;p=check

test_mem_leaks.sh: use libtool to invoke check_mem_leaks

The libtool documentation says the proper way to invoke the
compiled program before it is installed is to use libtool.

git-svn-id: svn+ssh://svn.code.sf.net/p/check/code/trunk@911 64e312b2-a51f-0410-8e61-82d0ca0eb02a
---

diff --git a/tests/test_mem_leaks.sh b/tests/test_mem_leaks.sh
index 081f744..e70c905 100755
--- a/tests/test_mem_leaks.sh
+++ b/tests/test_mem_leaks.sh
@@ -10,7 +10,7 @@ LEAK_MESSAGE="are definitely lost"
 # file for details on the leak.
 
 rm -f ${VALGRIND_LOG_FILE}
-valgrind --leak-check=full ${UNIT_TEST} 2>&1 | tee ${VALGRIND_LOG_FILE}
+libtool --mode=execute valgrind --leak-check=full ${UNIT_TEST} 2>&1 | tee ${VALGRIND_LOG_FILE}
 
 NUM_LEAKS=$(grep "${LEAK_MESSAGE}" ${VALGRIND_LOG_FILE} | wc -l)