If apitrace has its own old bundled copy of libbacktrace, better it should
update it to the latest version, which is
https://gcc.gnu.org/git/?p=gcc.git;a=tree;f=libbacktrace;h=7c4b8fb2fed26a7412bbed1f23976a0f568d0111;hb=HEAD
Incomplete DWARF5 support was added to it in December 2019 and importan
t-linux-gnu
> > Start 1: libbacktrace_btest
> > 1/6 Test #1: libbacktrace_btest ...***Exception: SegFault 0.11
> > sec
> > unrecognized DWARF version in .debug_info at 6
> >
> > Some dwz issues were mentioned in the runup to the mass rebuild, is this a
e_btest
> 1/6 Test #1: libbacktrace_btest ...***Exception: SegFault 0.11
> sec
> unrecognized DWARF version in .debug_info at 6
>
> Some dwz issues were mentioned in the runup to the mass rebuild, is this a
> related issue?
If apitrace has its own old bundled copy of libbackt
Test #1: libbacktrace_btest ...***Exception: SegFault 0.11
> sec
> unrecognized DWARF version in .debug_info at 6
>
> Some dwz issues were mentioned in the runup to the mass rebuild, is this a
> related issue?
More likely it doesn't understand dwarf5. GCC changed from default
version in .debug_info at 6
Some dwz issues were mentioned in the runup to the mass rebuild, is this a
related issue?
Thanks
Sandro
[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=60502198
___
devel mailing list -- devel@lists.fedoraproject.org
