From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16492 invoked by alias); 30 Aug 2009 18:00:29 -0000 Received: (qmail 16483 invoked by uid 22791); 30 Aug 2009 18:00:28 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout3.012.net.il (HELO mtaout3.012.net.il) (84.95.2.7) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 30 Aug 2009 18:00:18 +0000 Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KP700J00B50XV00@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Sun, 30 Aug 2009 21:00:15 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.144.38]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KP700KDVBCEUT00@i_mtaout3.012.net.il>; Sun, 30 Aug 2009 21:00:15 +0300 (IDT) Date: Sun, 30 Aug 2009 23:40:00 -0000 From: Eli Zaretskii Subject: Re: [RFA/RFC] Add dump and load command to process record and replay In-reply-to: To: Hui Zhu Cc: msnyder@vmware.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83skf99ob0.fsf@gnu.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT References: <4A948FF1.6000405@vmware.com> <4A949176.9060604@vmware.com> <831vmubitq.fsf@gnu.org> <83zl9i9xls.fsf@gnu.org> <4A99909E.7030302@vmware.com> <83ws4m9fhr.fsf@gnu.org> 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/msg00568.txt.bz2 > 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).  We cannot just say "dump record log to core file".  So > > I hereby revoke my approval of the patch for the manual. > > > > Agree with you, Eli. Do you have more better words on it? You know > my poor english. :) Something like this: @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.