From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: Abort backtrace when consecutive zero PCs?
Date: Wed, 15 Sep 2004 20:13:00 -0000 [thread overview]
Message-ID: <4148A1E6.5080306@gnu.org> (raw)
In-Reply-To: <41488E3B.nailC0Y21J3UA@mindspring.com>
> Andrew Cagney <cagney@gnu.org> wrote:
>
>>> While we definitly need to allow a backtrace through a single zero PC
>>> (for a NULL pointer call - signull.exp) should we make GDB abort when
>>> two or more consecutive frames have a zero PC?
>
>
> Perhaps abort it after an identical frame is seen a second time?
> It's not the zero-ness that kills us, it's the repetition.
For the case I'm looking at, successive frames have a zero PC and a
monotonic changing stack pointer, so there is no repetition.
Andrew
next prev parent reply other threads:[~2004-09-15 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 17:36 Andrew Cagney
2004-09-15 18:47 ` Michael Chastain
2004-09-15 20:13 ` Andrew Cagney [this message]
2004-09-15 22:13 ` Daniel Jacobowitz
2004-09-15 22:46 ` Andrew Cagney
2004-09-15 23:10 ` Daniel Jacobowitz
2004-09-15 23:35 ` 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=4148A1E6.5080306@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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