From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Abort backtrace when consecutive zero PCs?
Date: Wed, 15 Sep 2004 23:35:00 -0000 [thread overview]
Message-ID: <4148D139.2050409@gnu.org> (raw)
In-Reply-To: <20040915231021.GA30025@nevyn.them.org>
>>>want to reject zero PC followed by a normal
>>>> >(non-signal/dummy) frame, for exactly this reason...
>>
>>>
>>> That sounds like a NULL pointer function call, which is what signull.exp
>>> is all about.
>
>
> "followed" in the other direction. If we unwind a normal frame, and
> the next outer frame has a PC of zero, stop unwinding. We briefly had
> this check for "if the next frame is not the innermost frame" and that
> broke the equivalent of signull.exp; I think I proposed this in follow
> discussion to that.
Ah, now that makes sense.
Andrew
prev parent reply other threads:[~2004-09-15 23:35 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
2004-09-15 22:46 ` Andrew Cagney
2004-09-15 23:10 ` Daniel Jacobowitz
2004-09-15 23:35 ` Andrew Cagney [this message]
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=4148D139.2050409@gnu.org \
--to=cagney@gnu.org \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).