From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-301210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 14055 invoked by alias); 4 Dec 2009 22:36:49 -0000
Received: (qmail 13952 invoked by uid 48); 4 Dec 2009 22:36:33 -0000
Date: Fri, 04 Dec 2009 22:36:00 -0000
Subject: [Bug debug/42288]  New: please emit empty .debug_aranges section
X-Bugzilla-Reason: CC
Message-ID: <bug-42288-360@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2009-12/txt/msg00455.txt.bz2

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