aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlan Jenkins <alan-jenkins@tuffmail.co.uk>2010-03-02 09:59:44 +0000
committerAlan Jenkins <alan-jenkins@tuffmail.co.uk>2010-03-02 09:59:44 +0000
commit70ce1505e1d9b73060828552b695d0d4a4b57515 (patch)
tree64585831d9c4d8b6573ec47c0f7dec91abaa5daa
parent7bfbf4ba583f5da45795856accc9cf1c7bd5623f (diff)
downloadmodule-init-tools-alan-softdep-merge.tar.gz
tests: enable leak checking under --valgrindalan-softdep-merge
Since we have squashed all the leaks (or at least the ones that show up in the test suite), we can now use valgrind to look out for new ones. One of the reasons for this exercise is the index code, which mixes recursion with allocating and freeing memory. Memory leaks may not cause any problems at run-time - but they're still bugs, and bugs can make code harder to maintain.
-rwxr-xr-xtests/valgrind/valgrindme.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/valgrind/valgrindme.sh b/tests/valgrind/valgrindme.sh
index 0ab8a86..5d4cade 100755
--- a/tests/valgrind/valgrindme.sh
+++ b/tests/valgrind/valgrindme.sh
@@ -2,7 +2,7 @@
# Make sure it finds the real one this time.
PATH=`pwd`/tests/build:$PATH
-valgrind -q --num-callers=8 --suppressions=tests/valgrind/suppressions --log-fd=3 `basename $0` "$@" 3>tests/tmp/valgrind
+valgrind -q --num-callers=8 --leak-check=yes --suppressions=tests/valgrind/suppressions --log-fd=3 `basename $0` "$@" 3>tests/tmp/valgrind
ret=$?
if [ -s tests/tmp/valgrind ]; then