From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-12449-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 1402 invoked by alias); 4 Feb 2002 07:00:23 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 1272 invoked from network); 4 Feb 2002 07:00:20 -0000
Received: from unknown (HELO cygnus.com) (205.180.230.5)
  by sources.redhat.com with SMTP; 4 Feb 2002 07:00:20 -0000
Received: from telocity.telocity.com (taarna.sfbay.redhat.com [205.180.230.102])
	by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with SMTP id XAA06722;
	Sun, 3 Feb 2002 23:00:02 -0800 (PST)
Message-ID: <3C5E3062.A7B@redhat.com>
Date: Sun, 03 Feb 2002 23:00:00 -0000
From: Michael Snyder <msnyder@redhat.com>
X-Mailer: Mozilla 3.04 (Win95; I)
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@mvista.com>
CC: Jim Blandy <jimb@zenia.red-bean.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: Recognize bottom of stack on Linux
References: <200202040206.VAA21952@zenia.red-bean.com> <20020203222111.A17644@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-02/txt/msg00064.txt.bz2

Daniel Jacobowitz wrote:
> 
> On Sun, Feb 03, 2002 at 09:06:36PM -0500, Jim Blandy wrote:
> >
> > Now, some folks feel that GDB should show the whole stack, including
> > _start, __libc_start_main, and anything else that's there.  However,
> > this isn't the way GDB has ever traditionally behaved on native
> > targets.  So this patch makes GDB's backtraces end after main.
> >
> > 2002-02-03  Jim Blandy  <jimb@redhat.com>
> >
> >       * i386-linux-tdep.c (i386_linux_frame_chain): Stop the frame chain
> >       after `main', not just after the compilation unit containing the
> >       entry point.
> 
> Shouldn't we use func_frame_chain_valid instead of
> file_frame_chain_valid instead of duplicating this?
> 
> I don't understand why that function doesn't have more callers.  It
> seems that at least all non-embedded targets, or at the very least all
> Linux targets, should use it.

It doesn't always work as advertised...