From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20278 invoked by alias); 31 Aug 2009 02:52:26 -0000 Received: (qmail 20270 invoked by uid 22791); 31 Aug 2009 02:52:26 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_37,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-yw0-f176.google.com (HELO mail-yw0-f176.google.com) (209.85.211.176) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 31 Aug 2009 02:52:20 +0000 Received: by ywh6 with SMTP id 6so5469819ywh.0 for ; Sun, 30 Aug 2009 19:52:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.32.21 with SMTP id f21mr8037821ybf.225.1251687138587; Sun, 30 Aug 2009 19:52:18 -0700 (PDT) In-Reply-To: <83skf99ob0.fsf@gnu.org> References: <4A949176.9060604@vmware.com> <831vmubitq.fsf@gnu.org> <83zl9i9xls.fsf@gnu.org> <4A99909E.7030302@vmware.com> <83ws4m9fhr.fsf@gnu.org> <83skf99ob0.fsf@gnu.org> From: Hui Zhu Date: Mon, 31 Aug 2009 07:10:00 -0000 Message-ID: Subject: Re: [RFA/RFC] Add dump and load command to process record and replay To: Eli Zaretskii Cc: msnyder@vmware.com, gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-08/txt/msg00573.txt.bz2 On Mon, Aug 31, 2009 at 01:58, Eli Zaretskii wrote: >> From: Hui Zhu >> Date: Sun, 30 Aug 2009 11:20:32 +0800 >> Cc: Michael Snyder , gdb-patches@sourceware.org >> >> > This all needs to be said in the manual (in a form suitable for the >> > manual, omitting the technicalities and describing this from user >> > perspective). =A0We cannot just say "dump record log to core file". = =A0So >> > I hereby revoke my approval of the patch for the manual. >> > >> >> Agree with you, Eli. =A0Do you have more better words on it? =A0You know >> my poor english. =A0:) > > Something like this: > > =A0@kindex record dump > =A0@kindex rec dump > =A0@item record dump [@var{file}] > =A0@itemx rec dump [@var{file}] > =A0Dump the execution records of the inferior process to the named > =A0@var{file}. =A0If not specified, @var{file} defaults to > =A0@file{gdb_record.@var{pid}}, where @var{pid} is is the PID of the > =A0inferior process. > > =A0The file created by this command is actually a kind of core file, > =A0with an extra section that holds the recorded execution log. =A0The > =A0sections usually present in a core file capture the state of the > =A0inferior before the recording started, so that the file produced by > =A0this command can be used to replay the entire recorded session > =A0without the need to restore the initial state by some other means. > > Great. Thanks a lot. I make a new doc patch according to it. Hui 2009-08-31 Hui Zhu * gdb.texinfo (Process Record and Replay): Document the "record dump" commands. --- doc/gdb.texinfo | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) --- a/doc/gdb.texinfo +++ b/doc/gdb.texinfo @@ -5214,6 +5214,22 @@ 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 dump +@kindex rec dump +@item record dump [@var{file}] +@itemx rec dump [@var{file}] +Dump the execution records of the inferior process to the named +@var{file}. If not specified, @var{file} defaults to +@file{gdb_record.@var{pid}}, where @var{pid} is is the PID of the +inferior process. + +The file created by this command is actually a kind of core file, +with an extra section that holds the recorded execution log. The +sections usually present in a core file capture the state of the +inferior before the recording started, so that the file produced by +this command can be used to replay the entire recorded session +without the need to restore the initial state by some other means. @end table