On Thu, Nov 26, 2020 at 02:26:58PM +0100, Rainer Orth wrote:
> which shows that the problem is detected in the depths of
> libbacktrace's DWARF reader. There's something completely off in
> places, like line numbers well beyond the end of dwarf.c.
>
> TBH, I don't really feel like diving into the innards of libbacktrace
> and DWARF at this point to investigate.
Perhaps try binutils readelf -wi or dwarflint etc. to find out where things
go wrong, and then just look at the assembly and whether it matches what as
made out of it?
Jakub
