I have modified gdb to read the .debug_aranges section.
Currently, if this information does not exist for a
particular CU, gdb must scan the CU to find it.
This is necessary because there is no way to differentiate
between a section that is missing because it has no ranges,
and a section that is missing because it was stripped
or simply never created.

It would be helpful to gdb if gcc could emit .debug_aranges
even if there are no ranges to report.


-- 
           Summary: please emit empty .debug_aranges section
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tromey at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42288

Reply via email to