From: Michael Snyder <msnyder@redhat.com>
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
Date: Sun, 03 Feb 2002 23:00:00 -0000 [thread overview]
Message-ID: <3C5E3062.A7B@redhat.com> (raw)
In-Reply-To: <20020203222111.A17644@nevyn.them.org>
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...
next prev parent reply other threads:[~2002-02-04 7:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 18:21 Jim Blandy
2002-02-03 19:21 ` Daniel Jacobowitz
2002-02-03 23:00 ` Michael Snyder [this message]
2002-02-05 11:58 ` Jim Blandy
2002-02-05 13:57 ` Daniel Jacobowitz
2002-02-06 11:24 ` Jim Blandy
2002-02-06 16:09 ` Andrew Cagney
2002-03-30 21:56 ` Daniel Jacobowitz
2002-02-03 22:15 ` Eli Zaretskii
2002-02-04 11:02 ` Kevin Buettner
2002-02-04 17:32 ` Andrew Cagney
2002-02-04 17:42 ` Kevin Buettner
2002-02-04 17:44 ` Daniel Jacobowitz
2002-02-04 17:57 ` Michael Snyder
2002-02-04 18:55 ` Daniel Jacobowitz
2002-02-05 11:52 ` Jim Blandy
2002-02-06 16:02 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C5E3062.A7B@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zenia.red-bean.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox