Commit 50514774 authored by Rich Prohaska's avatar Rich Prohaska Committed by Yoni Fogel

refs[t:2673] check how valgrind detects memory leaks

git-svn-id: file:///svn/toku/tokudb@20777 c7de825b-a66e-492c-adef-691d508d4ae1
parent 0970d769
...@@ -44,7 +44,7 @@ test-pwrite4g.tdbrun: TEST_EXTRA_ARGS=. ...@@ -44,7 +44,7 @@ test-pwrite4g.tdbrun: TEST_EXTRA_ARGS=.
ifeq ($(VGRIND),) ifeq ($(VGRIND),)
./$< $(TEST_EXTRA_ARGS) $(SUMMARIZE_CMD) ./$< $(TEST_EXTRA_ARGS) $(SUMMARIZE_CMD)
else else
$(VGRIND) --error-exitcode=1 --quiet --leak-check=full -show-reachable=yes --log-file=$<.check.valgrind ./$< $(TEST_EXTRA_ARGS) >$<.check.output 2>&1; \ $(VGRIND) --error-exitcode=1 --quiet --leak-check=full --show-reachable=yes --log-file=$<.check.valgrind ./$< $(TEST_EXTRA_ARGS) >$<.check.output 2>&1; \
if [ $$? = 0 ] ; then \ if [ $$? = 0 ] ; then \
lines=`cat $<.check.valgrind | wc -l`; \ lines=`cat $<.check.valgrind | wc -l`; \
if [ $$lines -ne 0 ] ; then cat $<.check.valgrind; test 0 = 1; fi \ if [ $$lines -ne 0 ] ; then cat $<.check.valgrind; test 0 = 1; fi \
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment