binutils 2.32 update breaks debug symbols in disco

[Sebastien Bacher]

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

[Brian Murray (brian-murray)]

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.

[Brian Murray (brian-murray)]

An example of apport's behavior in this situation can be found in https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815703.

[Sebastien Bacher (seb128)]

The pointed commit is in 2.32 (see https://sourceware.org/bugzilla/show_bug.cgi?id=23919 for details) but that seems not enough since the disco-proposed version seems to not fix the issue from local testing

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Matthias Klose (doko)]

gdb 8.2.50.x handles this.

[Sebastien Bacher (seb128)]

Confirmed, that's fixed with that update