From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-18893-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 2065 invoked by alias); 4 Aug 2004 18:31: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 2057 invoked from network); 4 Aug 2004 18:31:03 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sourceware.org with SMTP; 4 Aug 2004 18:31:03 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i74IUwe3009932
	for <gdb@sources.redhat.com>; Wed, 4 Aug 2004 14:31:03 -0400
Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i74IUqa13538;
	Wed, 4 Aug 2004 14:30:52 -0400
Received: from gnu.org (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 7331B2B9D; Wed,  4 Aug 2004 14:30:46 -0400 (EDT)
Message-ID: <41112B56.3020304@gnu.org>
Date: Wed, 04 Aug 2004 18:31:00 -0000
From: Andrew Cagney <cagney@gnu.org>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040801
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com, Roland McGrath <roland@redhat.com>
Subject: Re: Identifying bottom-of-stack
References: <41110832.7040104@gnu.org> <20040804171602.GA18438@nevyn.them.org> <41112000.5040102@gnu.org> <20040804180151.GA20029@nevyn.them.org>
In-Reply-To: <20040804180151.GA20029@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-08/txt/msg00040.txt.bz2

>>>This would make debugging in the outermost frame quite annoying,
>>>> >wouldn't it?  We won't be able to find any frame relative variables.
>>
>>> 
>>> Why?  Frame relative variables us DW_AT_frame_base.
> 
> 
> You're right.  I still have the nagging feeling there's some other
> reason it matters, but since I can't think of specifics I'm probably
> just hallucinating again.

Two things that might help:

- dwarf2-frame incorrectly returns the CFA as the ``frame_base''.  Other 
stuff means that the value isn't used (well except for info frame).

- this relies on GDB permitting an unwind into, but not past, a frame 
with a NULL ID.  The old code would have stopped things one frame short.

Andrew