From: Orjan Friberg <orjan.friberg@axis.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: STEP_SKIPS_DELAY question, sort of
Date: Mon, 07 Jun 2004 12:12:00 -0000 [thread overview]
Message-ID: <40C45B95.9050309@axis.com> (raw)
In-Reply-To: <40B465E7.7050702@axis.com>
Orjan Friberg wrote:
>
> I'll go and have a closer look at STEP_SKIPS_DELAY.
Short recap: the MIPS checks if there's a breakpoint in the delay slot of the
instruction where GDB is about to resume execution. If so, GDB single-steps
that instruction before re-inserting the breakpoint.
For CRISv32, if there's a breakpoint on an instruction which has a delay slot,
we cannot re-insert the breakpoint when we're stopped in the delay slot (after
making one single-step), because the previous instruction will be re-executed
when returning from the delay slot.
I tried implementing a fix in handle_inferior_event (the MIPS fix is in
proceed). It seemed easier to step one more time when we find out that we need
to, rather than to determine beforehand that we're going to have to step twice
(and I couldn't determine how to pass that information).
The concept patch below illustrates what I'm trying to do; by setting
another_trap in the execution control state, by the time we get to keep_going we
won't insert the breakpoint and we'll instead continue single-stepping.
Comments? Is this the right approach at all?
Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.156
diff -u -r1.156 infrun.c
--- infrun.c 11 May 2004 23:30:31 -0000 1.156
+++ infrun.c 7 Jun 2004 11:44:19 -0000
@@ -1975,7 +1975,17 @@
/* Don't even think about breakpoints if just proceeded over a
breakpoint. */
if (stop_signal == TARGET_SIGNAL_TRAP && trap_expected)
- bpstat_clear (&stop_bpstat);
+ {
+ bpstat_clear (&stop_bpstat);
+
+ /* If we stepped into a delay slot, and the preceding instruction
+ will be re-executed when resuming, step again before re-inserting
+ the breakpoint. */
+ if (STEP_SKIPS_IN_DELAY_P
+ && breakpoint_here_p (read_pc () - 2)
+ && STEP_SKIPS_IN_DELAY (read_pc ()))
+ ecs->another_trap = 1;
+ }
else
{
/* See if there is a breakpoint at the current PC. */
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2004-06-07 12:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 17:14 Orjan Friberg
2004-05-21 20:25 ` Andrew Cagney
2004-05-24 9:15 ` Orjan Friberg
2004-05-24 18:15 ` Andrew Cagney
2004-05-25 11:53 ` Orjan Friberg
2004-05-25 21:14 ` Andrew Cagney
2004-05-26 9:39 ` Orjan Friberg
2004-05-26 17:39 ` Andrew Cagney
2004-06-07 12:12 ` Orjan Friberg [this message]
2004-06-07 12:42 ` Orjan Friberg
2004-06-07 13:09 ` Orjan Friberg
2004-06-07 15:08 ` Andrew Cagney
2004-06-09 9:48 ` Orjan Friberg
2004-06-09 16:00 ` Andrew Cagney
2004-06-14 12:09 ` Orjan Friberg
2004-06-16 14:53 ` Orjan Friberg
2004-06-24 18:25 ` Andrew Cagney
2004-10-01 11:26 ` Orjan Friberg
2004-10-25 20:18 ` Andrew Cagney
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=40C45B95.9050309@axis.com \
--to=orjan.friberg@axis.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.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