Confirmed, that's fixed with that update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb 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: Invalid Status in gdb package in Ubuntu: Fix Released Status in binutils source package in Disco: Invalid Status in gdb source package in Disco: Fix Released 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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
