From: Daniel Jacobowitz <drow@false.org>
To: Kei Sakamoto <sakamoto.kei@renesas.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/m32r] Fix breakpoint bug
Date: Mon, 25 Oct 2004 16:19:00 -0000 [thread overview]
Message-ID: <20041025153816.GA28488@nevyn.them.org> (raw)
In-Reply-To: <01b101c4ac37$3adbf950$5169910a@E5A02646>
On Thu, Oct 07, 2004 at 03:31:07PM +0900, Kei Sakamoto wrote:
> Hello,
>
> m32r-tdep.c can't handle breakpoints on instructions executed
> in parallel. It does not remove unnecessary parallel execution
> bit from instructions and causes illegal instruction errors.
>
> The attached patch fixes this problem.
>
> OK to commit?
>
> 2004-10-07 Kei Sakamoto <sakamoto.kei@renesas.com>
>
> * m32r-tdep.c (m32r_memory_insert_breakpoint): Remove
> unnecessary parallel execution bit.
> (m32r_memory_remove_breakpoint): Ditto.
> (m32r_breakpoint_from_pc): Update.
I'm curious about the little endian case:
+ else /* little-endian */
+ {
+ if ((addr & 3) == 0)
+ {
+ buf[0] = contents_cache[0];
+ buf[1] = contents_cache[1] & 0x7f;
+ buf[2] = bp_entry[1];
+ buf[3] = bp_entry[0];
}
Shouldn't the breakpoint be placed at buf[0] here rather than buf[2]?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-10-25 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 6:32 Kei Sakamoto
2004-10-18 6:43 ` [RFA/m32r] Unreviewed patch (breakpoint bug) Kei Sakamoto
2004-10-25 9:02 ` Kei Sakamoto
2004-11-01 1:08 ` Kei Sakamoto
2004-10-25 16:19 ` Daniel Jacobowitz [this message]
2004-10-26 5:45 ` [RFA/m32r] Fix breakpoint bug Kei Sakamoto
2004-11-04 0:21 ` Andrew Cagney
2004-11-04 0:50 ` Kei Sakamoto
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=20041025153816.GA28488@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=sakamoto.kei@renesas.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