From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20411-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 21791 invoked by alias); 30 Dec 2004 21:05:03 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 21758 invoked from network); 30 Dec 2004 21:04:57 -0000
Received: from unknown (HELO rwcrmhc12.comcast.net) (216.148.227.85)
  by sourceware.org with SMTP; 30 Dec 2004 21:04:57 -0000
Received: from lucon.org ([24.6.212.230]) by comcast.net (rwcrmhc12) with ESMTP
          id <2004123021045101400rrc00e>; Thu, 30 Dec 2004 21:04:57 +0000
Received: by lucon.org (Postfix, from userid 1000)
	id 7CB74640F4; Thu, 30 Dec 2004 13:04:51 -0800 (PST)
Date: Thu, 30 Dec 2004 21:05:00 -0000
From: "H. J. Lu" <hjl@lucon.org>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Daniel Jacobowitz <drow@false.org>, gcc@gcc.gnu.org,
	GDB <gdb@sources.redhat.com>
Subject: Re: Gdb generates location list without DW_AT_frame_base
Message-ID: <20041230210451.GA17966@lucon.org>
References: <41C9577D.3010509@redhat.com> <20041222182449.GA29407@lucon.org> <20041223034318.GA19580@nevyn.them.org> <20041230192424.GA16440@lucon.org> <20041230193618.GA16661@lucon.org> <20041230195642.GA16984@lucon.org> <20041230200720.GA11027@nevyn.them.org> <20041230202346.GA17311@lucon.org> <20041230202828.GA11668@nevyn.them.org> <1104440193.20792.38.camel@DYN253786YKT>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1104440193.20792.38.camel@DYN253786YKT>
User-Agent: Mutt/1.4.1i
X-SW-Source: 2004-12/txt/msg00136.txt.bz2

On Thu, Dec 30, 2004 at 03:56:33PM -0500, Daniel Berlin wrote:
> 
> > And what's in the location lists?  If it's DW_OP_fbreg, then I presume
> > it's a GCC bug.  According to my reading of the DWARF spec, anyway.
> It is.
> 
> I added code to tell it when not to use fbreg, but i only told it not to
> use fbreg in the location expression when we were outputting the
> frame_base attribute.
> 
> However, it appears we don't output a frame base attribute for external
> procedures, so we need to tell it it can't use if we don't have a frame
> base attribute.
> 
> You just need to change when loc_descriptor is called with a second
> parameter of true/1 to fix this.

Do you have a patch I can try?


H.J.