From: Daniel Jacobowitz <dan@debian.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sources.redhat.com, Nigel Stephens <nigel@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: MIPS/Linux: Single-stepping running away
Date: Thu, 07 Oct 2004 17:15:00 -0000 [thread overview]
Message-ID: <20041007171515.GA10186@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0410071758320.19346@perivale.mips.com>
On Thu, Oct 07, 2004 at 06:12:10PM +0100, Maciej W. Rozycki wrote:
> Hello,
>
> I've found two bugs in gdb that lead to single-stepping over branches
> failing under specific conditions -- the code tests register numbers
> instead of their values for a few variants of branches. Here is an
> obvious fix. It applies against the head.
>
> 2004-10-07 Maciej W. Rozycki <macro@mips.com>
>
> * mips-tdep.c (mips32_next_pc): Check the register's contents,
> not its number for BLEZ/BLEZL and BGTZ/BGTZL.
>
> Please apply.
I made the foolish mistake of mixing this fix into some larger MIPS
unwinder changes many months ago, which I've never had time to
disentangle. Sorry 'bout that.
This patch is indeed obvious; I'll check it in for you.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-10-07 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 17:12 Maciej W. Rozycki
2004-10-07 17:15 ` Daniel Jacobowitz [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=20041007171515.GA10186@nevyn.them.org \
--to=dan@debian.org \
--cc=gdb-patches@sources.redhat.com \
--cc=macro@linux-mips.org \
--cc=macro@mips.com \
--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