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>
This commit is contained in:
Michal Privoznik 2017-02-03 13:15:43 +01:00
parent 09a91f0528
commit a9595814ed

View File

@ -470,7 +470,8 @@ TESTS_ENVIRONMENT = \
$(VG) $(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 --suppressions=$(srcdir)/.valgrind.supp
valgrind: valgrind:
$(MAKE) check VG="libtool --mode=execute $(VALGRIND)" $(MAKE) check VG="libtool --mode=execute $(VALGRIND)"