Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [RFA] Submit process record and replay third time, 1/9
Date: Thu, 08 Jan 2009 05:44:00 -0000	[thread overview]
Message-ID: <daef60380901072144w79c11093g35e2cfb49db39ffb@mail.gmail.com> (raw)

[-- 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

             reply	other threads:[~2009-01-08  5:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08  5:44 teawater [this message]
2009-01-09 11:13 ` Joel Brobecker

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=daef60380901072144w79c11093g35e2cfb49db39ffb@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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