From: David Bremner <brem...@debian.org> As with the valgrind logs, we print a (very) brief summary and leave the log for inspection. --- performance-test/perf-test-lib.sh | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/performance-test/perf-test-lib.sh b/performance-test/perf-test-lib.sh index 10d05e0..9ee7661 100644 --- a/performance-test/perf-test-lib.sh +++ b/performance-test/perf-test-lib.sh @@ -126,13 +126,16 @@ memory_run () test_count=$(($test_count+1)) log_file=$log_dir/$test_count.log + talloc_log=$log_dir/$test_count.talloc printf "[ %d ]\t%s\n" $test_count "$1" - valgrind --leak-check=full --log-file="$log_file" $2 + NOTMUCH_TALLOC_REPORT="$talloc_log" valgrind --leak-check=full --log-file="$log_file" $2 awk '/LEAK SUMMARY/,/suppressed/ { sub(/^==[0-9]*==/," "); print }' "$log_file" echo + sed -n -e 's/.*[(]total *\([^)]*\)[)]/talloced at exit: \1/p' $talloc_log + echo } memory_done () -- 1.7.10.4