From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17813 invoked by alias); 1 Dec 2003 01:54:37 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 17695 invoked from network); 1 Dec 2003 01:54:35 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 1 Dec 2003 01:54:35 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1AQdGh-0002n9-6D; Sun, 30 Nov 2003 20:54:31 -0500 Date: Mon, 01 Dec 2003 01:54:00 -0000 From: Daniel Jacobowitz To: fnf@ninemoons.com Cc: gcc-bugs@gcc.gnu.org, gdb@sources.redhat.com Subject: Re: [RFC] Possible gcc/DWARF or gdb/DWARF problem Message-ID: <20031201015431.GA10708@nevyn.them.org> Mail-Followup-To: fnf@ninemoons.com, gcc-bugs@gcc.gnu.org, gdb@sources.redhat.com References: <200311292026.hATKQ3OI025805@fred.ninemoons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200311292026.hATKQ3OI025805@fred.ninemoons.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-12/txt/msg00001.txt.bz2 On Sat, Nov 29, 2003 at 01:26:03PM -0700, Fred Fish wrote: > I'd like to get some comments on whether this is a gcc/DWARF or > gdb/DWARF issue. If the consensus is that gdb is not doing the right > thing, then I'll chase the problem in gdb. If the consensus is that > it is gcc, then I'll file a formal gcc bug report. My guess is that > since gcc is generating the memory offset of a 1 byte object relative > to the frame pointer that the DW_AT_location for the big endian case > should be: > > DW_AT_location DW_OP_fbreg 3 I agree. We're describing an object in memory of size 1. It should be at the specified location, not padded. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer