platform_external_elfutils/tests/run-backtrace-data.sh, branch master Unnamed repository; edit this file 'description' to name the repository. tests: Use #/usr/bin/env bash in scripts that use bash 2020-06-15T22:32:30+00:00 Mark Wielaard mark@klomp.org 2020-06-15T22:25:47+00:00 bca87ed8a200b8845e82b06fa94e69cd637dfea3 Some systems don't have bash in /bin. Signed-off-by: Mark Wielaard <mark@klomp.org> 
Some systems don't have bash in /bin.

Signed-off-by: Mark Wielaard <mark@klomp.org>
tests: Improve backtrace-data SKIP message. 2018-11-28T12:58:31+00:00 Mark Wielaard mark@klomp.org 2018-11-28T12:58:31+00:00 63160fceaaac2f9bd13da7abf929907a5f723aab The backtrace-data testcase is x86_64 linux only because it uses its own set_initial_registers and scans its own /proc/pid/maps file. The SKIP message it gave on other platforms was misleading. It said "Unwinding not supported for this architecture". Change it to "x86_64 linux only test" to be less confusing. Signed-off-by: Mark Wielaard <mark@klomp.org> 
The backtrace-data testcase is x86_64 linux only because it uses its
own set_initial_registers and scans its own /proc/pid/maps file.
The SKIP message it gave on other platforms was misleading. It said
"Unwinding not supported for this architecture". Change it to
"x86_64 linux only test" to be less confusing.

Signed-off-by: Mark Wielaard <mark@klomp.org>
tests: Disable valgrind for core dumping and for self-introspecting tests. 2013-12-13T21:57:30+00:00 Mark Wielaard mjw@redhat.com 2013-12-13T21:42:46+00:00 7fc4929958ca78bd7b268014e9029d5ae1608822 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> 
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 for unwinder of x86*. 2013-12-02T19:54:28+00:00 Jan Kratochvil jan.kratochvil@redhat.com 2013-12-02T19:54:28+00:00 8ae9bc9d315be6ecbb97dd9754b9d8424b5a70f0 Signed-off-by: Jan Kratochvil <jan.kratochvil@redhat.com> 
Signed-off-by: Jan Kratochvil <jan.kratochvil@redhat.com>