summaryrefslogtreecommitdiff
path: root/t/valgrind
diff options
context:
space:
mode:
authorThomas Rast <trast@inf.ethz.ch>2013-03-31 08:00:17 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-04-01 14:45:41 (GMT)
commit95d9d5ec75d3549f00cac29cd33be899cfb4693a (patch)
tree698c3d8d05b7f078b61dd25c6963c1d54fa6407d /t/valgrind
parent952af3511c5dc7b7efd4c374d8b56d2c11d09d07 (diff)
downloadgit-95d9d5ec75d3549f00cac29cd33be899cfb4693a.zip
git-95d9d5ec75d3549f00cac29cd33be899cfb4693a.tar.gz
git-95d9d5ec75d3549f00cac29cd33be899cfb4693a.tar.bz2
tests --valgrind: provide a mode without --track-origins
With --valgrind=memcheck-fast, the tests run under memcheck but without the autodetected --track-origins. If you just run valgrind to see *if* there is any memory issue with your program, the extra information is not needed, and it comes at a roughly 30% hit in runtime. While it is possible to achieve the same through GIT_VALGRIND_OPTIONS, this should be more discoverable and hopefully encourage more users to run their tests with valgrind. Signed-off-by: Thomas Rast <trast@inf.ethz.ch> Acked-by: Johannes Schindelin <Johannes.Schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/valgrind')
-rwxr-xr-xt/valgrind/valgrind.sh2
1 files changed, 2 insertions, 0 deletions
diff --git a/t/valgrind/valgrind.sh b/t/valgrind/valgrind.sh
index 472ac2d..6b87c91 100755
--- a/t/valgrind/valgrind.sh
+++ b/t/valgrind/valgrind.sh
@@ -5,6 +5,8 @@ base=$(basename "$0")
TOOL_OPTIONS='--leak-check=no'
case "$GIT_VALGRIND_MODE" in
+memcheck-fast)
+ ;;
memcheck)
VALGRIND_VERSION=$(valgrind --version)
VALGRIND_MAJOR=$(expr "$VALGRIND_VERSION" : '[^0-9]*\([0-9]*\)')