From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Kevin Buettner <kevinb@redhat.com>,
Andrew Cagney <ac131313@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: RFA: Recognize bottom of stack on Linux
Date: Tue, 05 Feb 2002 11:52:00 -0000 [thread overview]
Message-ID: <np1yfzso2c.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <20020204204432.A31721@nevyn.them.org>
Daniel Jacobowitz <drow@mvista.com> writes:
> On Mon, Feb 04, 2002 at 06:41:10PM -0700, Kevin Buettner wrote:
> > On Feb 4, 8:32pm, Andrew Cagney wrote:
> >
> > [Regarding what, if anything, to show of the frames below main() in a
> > backtrace...]
> > > Perhaphs the correct fix is to let the user decide. Add a ``set
> > > stack-bottom-strategy ....'' :-)
> >
> > I think that may be best. I don't usually want to look at what's
> > below main(), but when I do, it's usually pretty important to me...
>
> Set backtrace-below-main perhaps?
I don't disagree, but I think it's a fix independent of my change.
I think the default should be to conceal stuff below main, since most
users aren't debugging their system startup code. Keep in mind that
this group has a skewed perspective on that, since that's exactly the
kind of thing we *do* spend our time worrying about.
next prev parent reply other threads:[~2002-02-05 19:52 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
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 [this message]
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=np1yfzso2c.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.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