diff options
| author | Karel Zak | 2018-03-21 12:23:22 +0100 |
|---|---|---|
| committer | Karel Zak | 2018-03-21 12:23:22 +0100 |
| commit | 51684b312e920c5d582c26ddfad0ae3bc8f22a07 (patch) | |
| tree | 416049f66d9650b84fa34122b262f399a7ddb07c /tests/functions.sh | |
| parent | tests: update lsmem (diff) | |
| download | kernel-qcow2-util-linux-51684b312e920c5d582c26ddfad0ae3bc8f22a07.tar.gz kernel-qcow2-util-linux-51684b312e920c5d582c26ddfad0ae3bc8f22a07.tar.xz kernel-qcow2-util-linux-51684b312e920c5d582c26ddfad0ae3bc8f22a07.zip | |
tests: use libtool to execute with valgrind
The libtool based build system uses scripts rather than real binaries
in $top_builddir. It's necessary to use libtool --mode=execute to call
valgrind for the real binary (from .libs/).
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'tests/functions.sh')
| -rw-r--r-- | tests/functions.sh | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/functions.sh b/tests/functions.sh index 0f991881a..2fb0ddb5f 100644 --- a/tests/functions.sh +++ b/tests/functions.sh @@ -393,6 +393,7 @@ function ts_run { # valgrind mode # if [ -n "$TS_VALGRIND_CMD" ]; then + libtool --mode=execute \ $TS_VALGRIND_CMD --tool=memcheck --leak-check=full \ --leak-resolution=high --num-callers=20 \ --log-file="$TS_VGDUMP" "$@" |