From: Michal Privoznik <mprivozn@redhat.com>
Date: Fri, 3 Feb 2017 12:15:43 +0000 (+0100)
Subject: tests: Trace re-executing processes with valgrind
X-Git-Tag: CVE-2017-2635~133
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a9595814ed093a63122c08655b623095e7898cd6;p=thirdparty%2Flibvirt.git

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 e923178f21..521728a3de 100644
--- 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)"