]> git.ipfire.org Git - thirdparty/libvirt.git/commit
projects / thirdparty / libvirt.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 09a91f0) | patch
tests: Trace re-executing processes with valgrind
authorMichal Privoznik <mprivozn@redhat.com>
Fri, 3 Feb 2017 12:15:43 +0000 (13:15 +0100)
committerMichal Privoznik <mprivozn@redhat.com>
Fri, 10 Feb 2017 09:25:44 +0000 (10:25 +0100)
commita9595814ed093a63122c08655b623095e7898cd6
tree22e0874e48e866286268c68a84745c18fc8a92datree | snapshot
parent09a91f0528bbe58ba0d8f9620fb978ad19f89052commit | diff
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>
tests/Makefile.am diff | blob | blame | history
Mirror of https://github.com/libvirt/libvirt.git