tests: Trace re-executing processes with valgrind

A lot of our tests re-execute themeselves after loading their
mock library. This, however, makes valgrind sad because currently
we do not tell it to trace the process after exec().

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>

diff --git a/tests/Makefile.am b/tests/Makefile.am
index e923178f21ad778a866b9b9f5f5dfe163e188f75..521728a3def4d70f0b228c4c144632245210b549 100644 (file)
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
@@ -470,7 +470,8 @@ TESTS_ENVIRONMENT =                         \
   $(VG)
 
 
-VALGRIND = valgrind --quiet --leak-check=full \
+VALGRIND = valgrind --quiet --leak-check=full --trace-children=yes \
+       --trace-children-skip="*/tools/virsh","*/tests/commandhelper" \
        --suppressions=$(srcdir)/.valgrind.supp
 valgrind:
        $(MAKE) check VG="libtool --mode=execute $(VALGRIND)"