[Bug tools/23673] TEST ./tests/backtrace-dwarf fails on s390x in at least 0.173

mark at klomp dot org sourceware-bugzilla@sourceware.org
Wed Oct 17 20:41:00 GMT 2018


--- Comment #20 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Michael Hudson-Doyle from comment #19)
> I see a similar looking failure on arm64 on Ubuntu 18.10:
> https://launchpadlibrarian.net/391377304/buildlog_ubuntu-cosmic-arm64.
> elfutils_0.170-0.5_BUILDING.txt.gz

So, if possible could you build with current git or 0.174 + the patch from
comment #14 or commit 69d6e67eee30c483ba53a8e1da1b3568033e3ddecommit

> I've gdb-ed this to the point that the key difference between a working
> system (Ubuntu 18.04) and the failing one is that libc.so.6 has a lot more
> entries in .eh_frame_hdr in the failing system. On 18.04 it fails to find a
> fde for abort() (or raise, I think) and unwinds using .debug_frame and that
> succeeds. On 18.10 it finds a fde for both raise and abort but fails to
> successfully unwind past abort using it. I don't know either why the newer
> libc.so.6 has a bigger eh_frame_hdr (it is glibc 2.28 vs 2.27 but also built
> with newer gcc and binutils) or why unwinding using eh_frame info fails.

In principle the .eh_frame and .debug_frame should provide the same CFI,
although encoded slightly differently. Maybe there is a difference? You should
be able to find both with eu-readelf --debug-dump=frame

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

More information about the Elfutils-devel mailing list