tests: Disable valgrind for core dumping and for self-introspecting tests.
authorMark Wielaard <mjw@redhat.com>
Fri, 13 Dec 2013 21:42:46 +0000 (22:42 +0100)
committerMark Wielaard <mjw@redhat.com>
Fri, 13 Dec 2013 21:57:30 +0000 (22:57 +0100)
commit7fc4929958ca78bd7b268014e9029d5ae1608822
tree3139dd1c55f84c09fbff01b5318b8f21dabe4d6b
parentb47e28a743afef4cd02fbe753c1526ed89c472c9
tests: Disable valgrind for core dumping and for self-introspecting tests.

The only tests that fork and exec are those that will then try to ptrace
attach the child for unwind testing. That won't work when the child is
also running under valgrind. So remove --trace-children=yes. Also disable
valgrind while dumping a core or for tests that try to inspect their own
state. They will get confused otherwise finding pieces of valgrind in
their maps.

Note we still seem to hit the following valgrind bug because the way we
map and unmap some shared libraries gets valgrind confused:
https://bugs.kde.org/show_bug.cgi?id=327427

Signed-off-by: Mark Wielaard <mjw@redhat.com>
tests/ChangeLog
tests/Makefile.am
tests/backtrace-subr.sh
tests/run-backtrace-data.sh
tests/run-backtrace-dwarf.sh