Last Comment Bug 837445 - GCC >= 4.8 bypasses checks for busted debugging with --gc-sections
: GCC >= 4.8 bypasses checks for busted debugging with --gc-sections
Status: NEW
Product: Core
Classification: Components
Component: Build Config (show other bugs)
: unspecified
: All Linux
-- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Gregory Szorc [:gps] (away until 2017-03-20)
Depends on:
  Show dependency treegraph
Reported: 2013-02-02 17:59 PST by Nathan Froyd [:froydnj]
Modified: 2013-02-02 17:59 PST (History)
1 user (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image Nathan Froyd [:froydnj] 2013-02-02 17:59:02 PST
Bug 670659 added a check to see whether --gc-sections harms the debugging experience.  The check relies on the presence of the .debug_ranges section in the compiled code.  However, it appears that -g with GCC 4.8 doesn't even produce .debug_ranges, but .debug_aranges, which I presume is more efficient.  The check should be made more robust.

(It turns out too that older versions of binutils don't necessarily understand the debugging output by newer versions of GCC, which can neuter the check, but I think we can leave that as caveat user, since the distros should be distributing compatible versions of everything.)

Note You need to log in before you can comment on or make changes to this bug.