[Bug libelf/28190] FAIL: run-backtrace-native.sh with glibc 2.34

[richard.purdie at linuxfoundation dot org via Elfutils-devel]

https://sourceware.org/bugzilla/show_bug.cgi?id=28190

richard.purdie at linuxfoundation dot org changed:

   What|Removed |Added

 CC||richard.purdie@linuxfoundat
   ||ion.org

--- Comment #1 from richard.purdie at linuxfoundation dot org ---
I can confirm that Yocto Project is seeing the same issue in its automated
testing on aarch64 and x86_64 with glibc 2.34

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libelf/28190] FAIL: run-backtrace-native.sh with glibc 2.34

[richard.purdie at linuxfoundation dot org via Elfutils-devel]

https://sourceware.org/bugzilla/show_bug.cgi?id=28190

--- Comment #4 from richard.purdie at linuxfoundation dot org ---
I tested the patch, thanks. This worked on our x86_64 target tests but not on
our aarch64 ones:

case 0: expected symname 'raise' got '__pthread_kill_internal'
/usr/lib/elfutils/ptest/tests/test-subr.sh: line 90: 12895 Aborted 
   $VALGRIND_CMD $program ${1+"$@"}
backtrace-child: no main
FAIL: run-backtrace-native.sh
case 0: expected symname 'raise' got '__pthread_kill_internal'
/usr/lib/elfutils/ptest/tests/test-subr.sh: line 90: 12946 Aborted 
   $VALGRIND_CMD $program ${1+"$@"}
backtrace-child-core.12942: no main
rmdir: failed to remove 'test-12934': Directory not empty
FAIL: run-backtrace-native-core.sh

The full log in case it is needed:
https://autobuilder.yocto.io/pub/non-release/20210804-19/testresults/qemuarm64-ptest/elfutils.log

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libelf/28190] FAIL: run-backtrace-native.sh with glibc 2.34

[richard.purdie at linuxfoundation dot org via Elfutils-devel]

https://sourceware.org/bugzilla/show_bug.cgi?id=28190

--- Comment #6 from richard.purdie at linuxfoundation dot org ---
Thanks, this version seems to resolve things!

-- 
You are receiving this mail because:
You are on the CC list for the bug.