From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26756 invoked by alias); 21 Feb 2003 18:02:20 -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 26734 invoked from network); 21 Feb 2003 18:02:19 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 21 Feb 2003 18:02:19 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18mJO3-0003ub-00; Fri, 21 Feb 2003 14:03:11 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18mHUn-0004Qv-00; Fri, 21 Feb 2003 13:02:01 -0500 Date: Fri, 21 Feb 2003 18:02:00 -0000 From: Daniel Jacobowitz To: Keith Walker Cc: Michal Ludvig , GDB Patches Subject: Re: [RFA] Location list support Message-ID: <20030221180201.GA17024@nevyn.them.org> Mail-Followup-To: Keith Walker , Michal Ludvig , GDB Patches References: <3E560801.6080703@suse.cz> <4.3.2.7.2.20030221173257.02997f68@mhsun1.maidenhead.arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.3.2.7.2.20030221173257.02997f68@mhsun1.maidenhead.arm.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-02/txt/msg00529.txt.bz2 On Fri, Feb 21, 2003 at 05:47:09PM +0000, Keith Walker wrote: > Michal, > > >The structure symbol itself is filled up with the first loclist entry > >found for this symbol (ie with the values for the lowest PC where the > >symbol is valid). > > Just to point out that the DWARF2 specification does not require the > entries in the location list to be specified in any specific order .... > therefore you shouldn't assume that the first entry is for the lowest PC > where the symbol is valid. > > > > Not related to your changes .... but I thought I would point out the > following issue once variables can be described using location lists: > > A location list allows for overlapping address ranges, ie. Where a > variables can be found in more that one place at a specific PC. Now for > reading the variable's value this means that you can read from any of the > specified locations. However if you allow writing of the variable's value > then the write should be performed to all the locations where the variable > can currently be found. Thanks. This'll probably be a FIXME for now... we're not quite set up for multiple locations. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer