binutils 2.32 update breaks debug symbols in disco
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
New
|
Undecided
|
Unassigned | ||
binutils (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Disco |
Invalid
|
High
|
Unassigned | ||
gdb (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Recently retracing started failing in disco, that seems to be due to the binutils 2.32 update
example
$ gdb gnome-control-
...
Reading symbols from gnome-control-
BFD: /usr/lib/
warning: File "/usr/lib/
(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:/
Changed in binutils (Ubuntu): | |
assignee: | Canonical Foundations Team (canonical-foundations) → nobody |
status: | New → In Progress |
Changed in binutils (Ubuntu): | |
status: | In Progress → New |
tags: | removed: rls-dd-incoming |
tags: | added: id-5c64ddcf31ae8e6f7cc51b89 |
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.