[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error (missing ebl abi_cfi hook)

2018-12-30 Thread kurt at roeckx dot be
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 --- Comment #10 from Kurt Roeckx --- In the mean time, I know the patch for mips was wrong, but the test suite seems to be happy with the current patch. Mips has many different ABIs, and I've mixed them up. The callee-saved registers aren't th

[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error (missing ebl abi_cfi hook)

2018-12-30 Thread kurt at roeckx dot be
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 --- Comment #9 from Kurt Roeckx --- I've fixed the issue on mips* in Debian, so it's now working on all Debian's release architectures. But some others still have this problem. -- You are receiving this mail because: You are on the CC list f

[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error (missing ebl abi_cfi hook)

2018-11-28 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 --- Comment #8 from Mark Wielaard --- (In reply to Mark Wielaard from comment #3) > (In reply to Kurt Roeckx from comment #2) > > PS: All arches except amd64 have "Unwinding not supported for this > > architecture" in run-backtrace-data.sh, wh

[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error (missing ebl abi_cfi hook)

2018-11-26 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 Mark Wielaard changed: What|Removed |Added Summary|varlocs |varlocs |dwarf_cfi_

[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error

2018-11-23 Thread kurt at roeckx dot be
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 --- Comment #6 from Kurt Roeckx --- Yes, they all 3 seem to be missing that callback. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error

2018-11-23 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 --- Comment #5 from Mark Wielaard --- (In reply to Kurt Roeckx from comment #4) > The varlocs test is calling dwarf_errmsg (-1) OK, that will show the last libdw error set on the current thread. In which case we might actually have a candidat

[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error

2018-11-23 Thread kurt at roeckx dot be
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 --- Comment #4 from Kurt Roeckx --- The varlocs test is calling dwarf_errmsg (-1) -- You are receiving this mail because: You are on the CC list for the bug.

[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error

2018-11-23 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 --- Comment #3 from Mark Wielaard --- (In reply to Kurt Roeckx from comment #2) > At least on mips I'm seeing an .eh_frame and .eh_frame_hdr section. It also > has some mips specific sections. Assuming they have "normal" types then that part

[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error

2018-11-21 Thread kurt at roeckx dot be
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 --- Comment #2 from Kurt Roeckx --- At least on mips I'm seeing an .eh_frame and .eh_frame_hdr section. It also has some mips specific sections. But note that various of the other tests say "Unwinding not supported for this architecture". Is

[Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error

2018-11-21 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 Mark Wielaard changed: What|Removed |Added CC||mark at klomp dot org --- Comment #1