提交 a9595814 编写于 作者: M Michal Privoznik

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: NMichal Privoznik <mprivozn@redhat.com>
上级 09a91f05
...@@ -470,7 +470,8 @@ TESTS_ENVIRONMENT = \ ...@@ -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)"
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册