From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, Nigel Stephens <nigel@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Do not unwind frames past NULL PC
Date: Fri, 22 Feb 2008 19:50:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0802221806130.21569@perivale.mips.com> (raw)
In-Reply-To: <20080222172056.GA1693@caradoc.them.org>
On Fri, 22 Feb 2008, Daniel Jacobowitz wrote:
> Similar changes have been proposed several times, but were controversial.
>
> http://sourceware.org/ml/gdb-patches/2006-05/msg00196.html
> http://sourceware.org/ml/gdb-patches/2006-07/msg00296.html
>
> and more recently:
>
> http://sourceware.org/ml/gdb-patches/2007-12/msg00004.html
Hmm, it looks it has been discussed deeply and fiercely enough for me not
to dare question the outcome (or the lack of), but given the situation
wouldn't it be reasonable to place a comment within the code of this
function stating that outermost frame determination has been deliberately
omitted so that cases like stack corruption are easier for people to
debug?
Maciej
next prev parent reply other threads:[~2008-02-22 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 17:21 Maciej W. Rozycki
2008-02-22 18:31 ` Daniel Jacobowitz
2008-02-22 19:50 ` Maciej W. Rozycki [this message]
2008-02-25 19:19 ` Maciej W. Rozycki
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=Pine.LNX.4.61.0802221806130.21569@perivale.mips.com \
--to=macro@mips.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=nigel@mips.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