From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: macro@mips.com
Cc: gdb-patches@sourceware.org, chris@mips.com, macro@linux-mips.org
Subject: Re: mips-tdep.c: Adjust breakpoints in branch delay slots
Date: Thu, 24 May 2007 18:21:00 -0000 [thread overview]
Message-ID: <200705241821.l4OIL5wX018281@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.61.0705241853450.21951@perivale.mips.com> (macro@mips.com)
> Date: Thu, 24 May 2007 19:07:46 +0100 (BST)
> From: "Maciej W. Rozycki" <macro@mips.com>
>
> Hello,
>
> This is a change that makes breakpoints requested in a branch or jump
> delay slot be moved to the preceding instruction. This removes a
> confusion that arises when such a breakpoint is hit and the resulting
> message like this:
>
> (gdb) break *0x00400670
> Breakpoint 1 at 0x400670: file foo.c, line 12.
> (gdb) run
> Starting program: .../foo
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> main (argc=1, argv=0x7fd7c874) at foo.c:12
> 12 }
> (gdb) x /2i $pc
> 0x40066c <main+12>: jr ra
> 0x400670 <main+16>: move v0,zero
>
> This change has been tested natively for mips-unknown-linux-gnu and
> remotely for mipsisa32-sde-elf, using mips-sim-sde32/-EB,
> mips-sim-sde32/-mips16/-EB, mips-sim-sde32/-EL and
> mips-sim-sde32/-mips16/-EL as the targets, with no regressions.
>
> 2007-05-24 Chris Dearman <chris@mips.com>
> Maciej W. Rozycki <macro@mips.com>
>
> * mips-tdep.c (mips32_instruction_has_delay_slot): New function.
> (mips16_instruction_has_delay_slot): Likewise.
> (mips_segment_boundary): Likewise.
> (mips_adjust_breakpoint_address): Likewise.
> (mips_gdbarch_init): Use mips_adjust_breakpoint_address.
>
> OK to apply?
Do we have a testcase for this? I also would like to test this on
OpenBSD/mips64. Unfortunately I won't be able to test this in the
next three weeks. Can this wait until then?
next prev parent reply other threads:[~2007-05-24 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 18:08 Maciej W. Rozycki
2007-05-24 18:21 ` Mark Kettenis [this message]
2007-05-24 18:31 ` Daniel Jacobowitz
[not found] ` <Pine.LNX.4.61.0705251217190.13913@perivale.mips.com>
2007-05-25 12:50 ` Maciej W. Rozycki
2007-05-25 13:16 ` Maciej W. Rozycki
[not found] ` <Pine.LNX.4.61.0705251318500.13913@perivale.mips.com>
2007-05-25 13:19 ` Daniel Jacobowitz
2007-06-15 14:38 ` Maciej W. Rozycki
2007-05-25 13:21 ` Maciej W. Rozycki
2007-05-25 13:26 ` Daniel Jacobowitz
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=200705241821.l4OIL5wX018281@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=chris@mips.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@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