From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-67771-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 10707 invoked by alias); 17 Oct 2009 19:11:18 -0000
Received: (qmail 10699 invoked by uid 22791); 17 Oct 2009 19:11:18 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 17 Oct 2009 19:11:14 +0000
Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) 	by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 1898127024; 	Sat, 17 Oct 2009 12:11:13 -0700 (PDT)
Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) 	by mailhost4.vmware.com (Postfix) with ESMTP id 0A5A9C9BA4; 	Sat, 17 Oct 2009 12:11:12 -0700 (PDT)
Message-ID: <4ADA1577.4000100@vmware.com>
Date: Sat, 17 Oct 2009 19:11:00 -0000
From: Michael Snyder <msnyder@vmware.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20080411)
MIME-Version: 1.0
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)
Content-Type: multipart/mixed;  boundary="------------070300010406030806060707"
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-10/txt/msg00394.txt.bz2

This is a multi-part message in MIME format.
--------------070300010406030806060707
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-length: 38

The fourth part of the trilogy.  ;-)


--------------070300010406030806060707
Content-Type: text/plain;
 name="docs.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="docs.txt"
Content-length: 2178

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
 
 

--------------070300010406030806060707--