From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-67775-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 18538 invoked by alias); 17 Oct 2009 20:16:35 -0000
Received: (qmail 18529 invoked by uid 22791); 17 Oct 2009 20:16:35 -0000
X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 17 Oct 2009 20:16:30 +0000
Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0KRO00N00DH61400@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Sat, 17 Oct 2009 22:16:27 +0200 (IST)
Received: from HOME-C4E4A596F7 ([87.70.117.47]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KRO00JJODNEKN60@a-mtaout21.012.net.il>; Sat, 17 Oct 2009 22:16:27 +0200 (IST)
Date: Sat, 17 Oct 2009 20:16:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA, 4 of 3] save/restore process record, part 4 (docs and news)
In-reply-to: <4ADA1577.4000100@vmware.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: gdb-patches@sourceware.org, teawater@gmail.com
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83ljj9hj6n.fsf@gnu.org>
References: <4ADA1577.4000100@vmware.com>
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/msg00398.txt.bz2

> Date: Sat, 17 Oct 2009 12:05:27 -0700
> From: Michael Snyder <msnyder@vmware.com>
> 
> The fourth part of the trilogy.  ;-)

Thanks.

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

This needs to state the name of the node where you made the changes.

> +* New commands
> +
> +record save <filename> -- Save a 'process record' execution log to a file.
> +record restore <filename -- Restore an earlier 'process record' session.

Please format these as we did with other new commands in NEWS.

> +Save the execution log of the inferior process into a modified core file.

"Modified" is too overloaded.  Suggest "specially formatted" instead.

> +This execution log can then be debugged using the @code{process record}

Well, you can't really "debug the execution log", can you?  How about

  You can then replay this execution log as if you recorded it in this
  @value{GDBN} session.

?