The retracers do not treat this as a failure because apport returns 0
when retracing the crash and that's because gdb also returns 0 as I
believe this is just a warning from gdb. That being said there is no
record of this failure in the retracers and it would not have been
noticed if not for seb128, so there is some room for improvement in how
the retracers / apport handle this situation.
** Also affects: apport
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1815774
Title:
binutils 2.32 update breaks debug symbols in disco
Status in Apport:
New
Status in binutils package in Ubuntu:
New
Bug description:
Recently retracing started failing in disco, that seems to be due to
the binutils 2.32 update
example
$ gdb gnome-control-center
...
Reading symbols from gnome-control-center...BFD:
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug:
unable to initialize decompress status for section .debug_aranges
BFD:
/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug:
unable to initialize decompress status for section .debug_aranges
warning: File
"/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has
no build-id, file skipped
(no debugging symbols found)...done.
Rebuilding the package with binutils 2.31 installed fixes the issue. Googling
for the warning lead to an arch bug pointing out that upstream commit as fixing
the issue
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1815774/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
