[RFA] Submit process record and replay third time, 1/9

[RFA] Submit process record and replay third time, 1/9

[teawater]

[-- Attachment #1: Type: text/plain, Size: 682 bytes --]

This patch is add two function pointers interface to GDB architecture
support layer for process record and replay.

After use this patch, still need:
cd src/gdb/
./gdbarch.sh
cp new-gdbarch.c gdbarch.c
cp new-gdbarch.h gdbarch.h

2009-01-08  Hui Zhu  <teawater@gmail.com>

	GDBARCH interface for process record and replay.

	* gdbarch.sh (process_record): This interface point to the
	function that records the inferior execute log.
	(process_record_dasm): This interface points to the function
	that will be called to set inferior status according to the
	instruction in replay mode.

	2008-12-28  Michael Snyder  <msnyder@vmware.com>
	* Comments, spelling, white space clean-ups.

[-- Attachment #2: 1-gdbarch.txt --]
[-- Type: text/plain, Size: 476 bytes --]

--- a/gdbarch.sh
+++ b/gdbarch.sh
@@ -698,6 +698,10 @@
 # Set if the address in N_SO or N_FUN stabs may be zero.
 v:int:sofun_address_maybe_missing:::0:0::0
 
+# For the process record and replay target.
+M:int:process_record:CORE_ADDR addr:addr
+M:void:process_record_dasm:void
+
 # Signal translation: translate inferior's signal (host's) number into
 # GDB's representation.
 m:enum target_signal:target_signal_from_host:int signo:signo::default_target_signal_from_host::0

Re: [RFA] Submit process record and replay third time, 1/9

[Joel Brobecker]

> +# For the process record and replay target.
> +M:int:process_record:CORE_ADDR addr:addr
> +M:void:process_record_dasm:void

I haven't really followed the last discussions about recording
and reverse debugging. If these two methods are the way we decide
to go, could we document exactly what each method is expected
to do? This will help future implementors, I think.

-- 
Joel