Bug 24220 - [2.32 Regression] gdb cannot read read separate debug info generated by binutils 2.32
Summary: [2.32 Regression] gdb cannot read read separate debug info generated by binut...
Status: RESOLVED FIXED
Alias: None
Product: binutils
Classification: Unclassified
Component: binutils (show other bugs)
Version: 2.32
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-13 19:16 UTC by Matthias Klose
Modified: 2019-02-25 13:47 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments
binary and separate debuginfo (41.79 KB, application/x-xz)
2019-02-13 19:16 UTC, Matthias Klose
Details
binary and separate debuginfo (2.31.1) (41.85 KB, application/x-xz)
2019-02-13 19:18 UTC, Matthias Klose
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Klose 2019-02-13 19:16:04 UTC
Created attachment 11606 [details]
binary and separate debuginfo

Seen at least with 2.32 on x86_64.

$ gdb hello
GNU gdb (Ubuntu 8.2.1-0ubuntu1) 8.2.1
[...]

Reading symbols from hello...BFD: /usr/lib/debug/.build-id/3f/a492da4dec8933b2173d353444f17547e4b342.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/3f/a492da4dec8933b2173d353444f17547e4b342.debug: unable to initialize decompress status for section .debug_aranges

warning: File "/usr/lib/debug/.build-id/3f/a492da4dec8933b2173d353444f17547e4b342.debug" has no build-id, file skipped
(no debugging symbols found)...done.
Comment 1 Matthias Klose 2019-02-13 19:18:44 UTC
Created attachment 11607 [details]
binary and separate debuginfo (2.31.1)

works when linked with binutils 2.31.1.
Comment 2 Matthias Klose 2019-02-13 19:50:52 UTC
hmm, this works with a gdb built from the trunk
Comment 3 Nick Clifton 2019-02-19 15:32:22 UTC
(In reply to Matthias Klose from comment #2)
> hmm, this works with a gdb built from the trunk

Does this mean that this is a GDB issue ?  

Which version of GDB were you using when you discovered the failure ?
Assuming that it was from a branch of GDB, then it is likely that the
problem has been fixed on the mainline but not backported to that
branch.  Check out PR 23919 as a possible culprit.

Cheers
  Nick
Comment 4 Matthias Klose 2019-02-25 13:08:30 UTC
yes, this is seen with gdb 8.2.1. Backporting that patch to gdb solves the issue and gdb is able to read both the unfixed and fixed compressed debug sections.
Comment 5 Nick Clifton 2019-02-25 13:47:40 UTC
OK, I am closing this PR then.