Re: eh_frame is debug info too

2018-09-18 Thread Sasha Da Rocha Pinheiro
It's not working but I'm fixing it. We don't use Elfutils to find the corresponding separate debug info. It was already implemented by searching the gnu_debuglink section and getting the info. Sasha From: Mark Wielaard Sent: Tuesday, September 18, 2018 6:36 AM To: Sasha Da Rocha Pinheiro; el

[Bug tools/23673] TEST ./tests/backtrace-dwarf fails on s390x in 0.174 release

2018-09-18 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23673 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Re: eh_frame is debug info too

2018-09-18 Thread Mark Wielaard
Hi Sasha, On Mon, 2018-09-17 at 21:18 +, Sasha Da Rocha Pinheiro wrote: > So my point is: can we make dwarf_begin_elf() open binaries that only > contain ".eh_frame" to further be able to call dwarf_cfi_addrframe? I see your point and we have been more relax in determining what is or isn't a

[Bug tools/23673] TEST ./tests/backtrace-dwarf fails on s390x in 0.174 release

2018-09-18 Thread mliska at suse dot cz
https://sourceware.org/bugzilla/show_bug.cgi?id=23673 --- Comment #4 from Martin Liska --- Created attachment 11257 --> https://sourceware.org/bugzilla/attachment.cgi?id=11257&action=edit openSUSE build log I'm attaching my build log. In general, I guess following flags are used: -std=gnu99 -