From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@specifix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: Fix check for no-saved-pc
Date: Fri, 30 Nov 2007 23:00:00 -0000 [thread overview]
Message-ID: <20071130230045.GA24809@caradoc.them.org> (raw)
In-Reply-To: <1196462431.2501.164.camel@localhost.localdomain>
On Fri, Nov 30, 2007 at 02:40:31PM -0800, Michael Snyder wrote:
> There's a check in get_prev_frame to see if the next saved pc
> is zero. I think it has an off-by-one error, and is checking
> for the pc of the wrong frame.
Mark K. and I have had roughly a month's worth of discussion on this
check over the last two years; it's where it is on purpose. Here's
the last conversation:
http://sourceware.org/ml/gdb-patches/2006-05/msg00196.html
http://sourceware.org/ml/gdb-patches/2006-07/msg00296.html
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-11-30 23:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 22:53 Michael Snyder
2007-11-30 23:00 ` Daniel Jacobowitz [this message]
2007-12-01 1:50 ` Michael Snyder
2007-12-04 2:06 ` Michael Snyder
2007-12-04 18:05 ` Mark Kettenis
2007-12-04 23:25 ` Michael Snyder
2007-12-12 19:42 ` Michael Snyder
2007-12-16 20:08 ` Mark Kettenis
2007-12-17 18:43 ` Michael Snyder
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=20071130230045.GA24809@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@specifix.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