To do: we should always check for memory leaks with valgrind. However, there are still a few left in error handling that would trip the test. --- src/compiler/test/patches | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/src/compiler/test/patches b/src/compiler/test/patches index f567a5c..1a31fa3 100755 --- a/src/compiler/test/patches +++ b/src/compiler/test/patches @@ -4,6 +4,15 @@ ############################################################################### # +# If we're going to spend the time to run under valgrind, make the most +# of it. +# + +if [ "$VALGRIND" ]; then + VALGRIND="$VALGRIND --leak-check=full --show-reachable=yes" +fi + +# # We explicitly list all the known patches here so that any local additions # won't interfere. # -- 1.7.1 _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode
