[RFA] Submit process record and replay fourth time, 5/8

Hui Zhu teawater@gmail.com
Wed Mar 25 07:23:00 GMT 2009


Update follow "3-record_target.txt".

Thanks,
Hui

On Sun, Mar 22, 2009 at 00:02, Hui Zhu <teawater@gmail.com> wrote:
> This patch to add some process record and replay to infrun.c.
>
> Code for function "use_displaced_stepping" is make sure that displaced
> stepping function will disable when process record and replay target
> is opened.  Because process record and replay target doesn't support
> displaced stepping function.
>
> Code for function "proceed" is call function "record_not_record_set"
> to set process record and replay target doesn't record the execute
> log.  Because when GDB resume the inferior, process record and replay
> target doesn't need to record the memory and register store operation
> of GDB.
>
> 2009-03-21  Hui Zhu  <teawater@gmail.com>
>
>        * infrun.c (use_displaced_stepping): Return false if process
>        record and replay target is used.
>        (proceed): Call function "record_not_record_set" if pocess
>        record and replay target is used.
>
>        2008-12-26  Michael Snyder  <msnyder@vmware.com>
>        * infrun.c (proceed): Don't call record_not_record_set.
>
-------------- next part --------------
---
 infrun.c |   12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

--- a/infrun.c
+++ b/infrun.c
@@ -49,6 +49,8 @@
 #include "mi/mi-common.h"
 #include "event-top.h"
 
+#include "record.h"
+
 /* Prototypes for local functions */
 
 static void signals_info (char *, int);
@@ -603,7 +605,8 @@ use_displaced_stepping (struct gdbarch *
   return (((can_use_displaced_stepping == can_use_displaced_stepping_auto
 	    && non_stop)
 	   || can_use_displaced_stepping == can_use_displaced_stepping_on)
-	  && gdbarch_displaced_step_copy_insn_p (gdbarch));
+	  && gdbarch_displaced_step_copy_insn_p (gdbarch)
+	  && current_target.to_stratum != record_stratum);
 }
 
 /* Clean out any stray displaced stepping state.  */
@@ -2109,6 +2112,10 @@ adjust_pc_after_break (struct execution_
   if (software_breakpoint_inserted_here_p (breakpoint_pc)
       || (non_stop && moribund_breakpoint_here_p (breakpoint_pc)))
     {
+      struct cleanup *old_cleanups = NULL;
+      if (current_target.to_stratum == record_stratum)
+	old_cleanups = record_gdb_operation_disable_set ();
+
       /* When using hardware single-step, a SIGTRAP is reported for both
 	 a completed single-step and a software breakpoint.  Need to
 	 differentiate between the two, as the latter needs adjusting
@@ -2132,6 +2139,9 @@ adjust_pc_after_break (struct execution_
 	  || !currently_stepping (ecs->event_thread)
 	  || ecs->event_thread->prev_pc == breakpoint_pc)
 	regcache_write_pc (regcache, breakpoint_pc);
+
+      if (old_cleanups)
+	do_cleanups (old_cleanups);
     }
 }
 


More information about the Gdb-patches mailing list