From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2936 invoked by alias); 4 Jan 2002 17:13:35 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 2893 invoked from network); 4 Jan 2002 17:13:33 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 4 Jan 2002 17:13:33 -0000 Received: from drow by nevyn.them.org with local (Exim 3.33 #1 (Debian)) id 16MXuE-0007bA-00; Fri, 04 Jan 2002 12:13:22 -0500 Date: Fri, 04 Jan 2002 09:13:00 -0000 From: Daniel Jacobowitz To: Daniel Berlin Cc: Richard Henderson , gdb-patches@sources.redhat.com Subject: Re: [RFC] Partial support for dwarf3 DW_AT_ranges Message-ID: <20020104121322.A29086@nevyn.them.org> Mail-Followup-To: Daniel Berlin , Richard Henderson , gdb-patches@sources.redhat.com References: <20011231003448.A3399@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i X-SW-Source: 2002-01/txt/msg00025.txt.bz2 On Fri, Jan 04, 2002 at 10:21:04AM -0500, Daniel Berlin wrote: > On Mon, 31 Dec 2001, Richard Henderson wrote: > > > GCC began emitting DW_AT_ranges back in September to deal with > > lexical scopes made discontiguous by basic block reordering. > > > > As of today, it may also create discontiguous lexical scopes > > due to scheduling. (Before today under the same circumstances > > we'd lose track of which instructions belonged to which scope > > and fail to emit any debug information whatsoever.) > > > > However, GDB doesn't recognize DW_AT_ranges as a valid way of > > marking a lexical scope, which causes it to discard the scope > > entirely. Which is probably the least useful thing that could > > be done. > > > > The following does not add proper support for discontiguous > > address ranges. I couldn't figure out how to do that in any > > way that wasn't horribly invasive. > Horribly invasive to the dwarf2 reader, or to other pieces of gdb? Other places in GDB; the framework isn't there to record it. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer