aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2008-10-18 03:24:34 +0000
committerPedro Alves <palves@redhat.com>2008-10-18 03:24:34 +0000
commit4058b839704e5992381636e1e22c8969526d796b (patch)
tree013fe3e390dd07d145bfef5ea6e606e13d9e751d /gdb
parentb4f899bb85b2f6a62878b853fd6a9c67c77b2be9 (diff)
downloadgdb-4058b839704e5992381636e1e22c8969526d796b.zip
gdb-4058b839704e5992381636e1e22c8969526d796b.tar.gz
gdb-4058b839704e5992381636e1e22c8969526d796b.tar.bz2
* infrun.c (adjust_pc_after_break): Do nothing if executing in
reverse.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/ChangeLog5
-rw-r--r--gdb/infrun.c29
2 files changed, 34 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 92dab51..7490ff3 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2008-10-18 Pedro Alves <pedro@codesourcery.com>
+
+ * infrun.c (adjust_pc_after_break): Do nothing if executing in
+ reverse.
+
2008-10-17 Pedro Alves <pedro@codesourcery.com>
* infcmd.c (GO_USAGE): Delete.
diff --git a/gdb/infrun.c b/gdb/infrun.c
index 5114501..0aab669 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -1826,6 +1826,35 @@ adjust_pc_after_break (struct execution_control_state *ecs)
if (ecs->ws.value.sig != TARGET_SIGNAL_TRAP)
return;
+ /* In reverse execution, when a breakpoint is hit, the instruction
+ under it has already been de-executed. The reported PC always
+ points at the breakpoint address, so adjusting it further would
+ be wrong. E.g., consider this case on a decr_pc_after_break == 1
+ architecture:
+
+ B1 0x08000000 : INSN1
+ B2 0x08000001 : INSN2
+ 0x08000002 : INSN3
+ PC -> 0x08000003 : INSN4
+
+ Say you're stopped at 0x08000003 as above. Reverse continuing
+ from that point should hit B2 as below. Reading the PC when the
+ SIGTRAP is reported should read 0x08000001 and INSN2 should have
+ been de-executed already.
+
+ B1 0x08000000 : INSN1
+ B2 PC -> 0x08000001 : INSN2
+ 0x08000002 : INSN3
+ 0x08000003 : INSN4
+
+ We can't apply the same logic as for forward execution, because
+ we would wrongly adjust the PC to 0x08000000, since there's a
+ breakpoint at PC - 1. We'd then report a hit on B1, although
+ INSN1 hadn't been de-executed yet. Doing nothing is the correct
+ behaviour. */
+ if (execution_direction == EXEC_REVERSE)
+ return;
+
/* If this target does not decrement the PC after breakpoints, then
we have nothing to do. */
regcache = get_thread_regcache (ecs->ptid);