From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: Abort backtrace when consecutive zero PCs?
Date: Wed, 15 Sep 2004 22:13:00 -0000 [thread overview]
Message-ID: <20040915221329.GA28732@nevyn.them.org> (raw)
In-Reply-To: <41487D1D.7040504@gnu.org>
On Wed, Sep 15, 2004 at 01:34:21PM -0400, Andrew Cagney wrote:
> Hello,
>
> One backtrace infinite loop case I've noticed (especially on ia64) is
> where successive frames all have a zero PC.
>
> 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?
>
> (mumble something about a runtime option)
>
> thoughts?
I still think that you want to reject zero PC followed by a normal
(non-signal/dummy) frame, for exactly this reason...
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-09-15 22: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
2004-09-15 22:13 ` Daniel Jacobowitz [this message]
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=20040915221329.GA28732@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.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