Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	  Eli Zaretskii <eliz@gnu.org>,  Hui Zhu <teawater@gmail.com>
Subject: [RFA, 4 of 3] save/restore process record, part 4 (docs and news)
Date: Sat, 17 Oct 2009 19:11:00 -0000	[thread overview]
Message-ID: <4ADA1577.4000100@vmware.com> (raw)

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

The fourth part of the trilogy.  ;-)


[-- Attachment #2: docs.txt --]
[-- Type: text/plain, Size: 2178 bytes --]

2009-10-17  Hui Zhu  <teawater@gmail.com>
	    Michael Snyder  <msnyder@vmware.com>

	* docs/gdb.texinfo: Document record save/restore commands.
	* NEWS: Mention record save/restore commands.

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.334
diff -u -p -r1.334 NEWS
--- NEWS	15 Oct 2009 19:28:52 -0000	1.334
+++ NEWS	17 Oct 2009 19:08:11 -0000
@@ -11,6 +11,11 @@ Xilinx MicroBlaze		microblaze-*-*
 
 Xilinx MicroBlaze		microblaze
 
+* New commands
+
+record save <filename> -- Save a 'process record' execution log to a file.
+record restore <filename -- Restore an earlier 'process record' session.
+
 *** Changes in GDB 7.0
 
 * GDB now has an interface for JIT compilation.  Applications that
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.633
diff -u -p -r1.633 gdb.texinfo
--- doc/gdb.texinfo	12 Oct 2009 01:59:54 -0000	1.633
+++ doc/gdb.texinfo	17 Oct 2009 19:08:12 -0000
@@ -5348,6 +5348,26 @@ When record target runs in replay mode (
 subsequent execution log and begin to record a new execution log starting
 from the current address.  This means you will abandon the previously
 recorded ``future'' and begin recording a new ``future''.
+
+@kindex record save
+@kindex rec save
+@item record save [@var{file}]
+@itemx rec save [@var{file}]
+Save the execution log of the inferior process into a modified core file.
+The optional argument @var{file} specifies the file name in which to
+save the execution log.  If not specified, the file name defaults
+to @file{gdb_record.@var{pid}}, where @var{pid} is is the PID of the
+inferior process.
+
+@kindex record restore
+@kindex rec restore
+@item record restore [@var{file}]
+@itemx rec restore [@var{file}]
+Restore the execution log of an earlier session from the file @var{file}
+(required), which has been created using the command @code{record save}.
+This execution log can then be debugged using the @code{process record}
+target, in replay mode, just like replaying a live debugging session.
+
 @end table
 
 

             reply	other threads:[~2009-10-17 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-17 19:11 Michael Snyder [this message]
2009-10-17 20:16 ` Eli Zaretskii
2009-10-17 22:25   ` Michael Snyder
2009-10-18  4:08     ` Eli Zaretskii
2009-10-18  4:13       ` Michael Snyder
2009-10-18 18:37         ` Eli Zaretskii
2009-10-22 19:42           ` Michael Snyder

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=4ADA1577.4000100@vmware.com \
    --to=msnyder@vmware.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=teawater@gmail.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