From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8849 invoked by alias); 30 Aug 2009 02:56:30 -0000 Received: (qmail 8840 invoked by uid 22791); 30 Aug 2009 02:56:29 -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 mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 30 Aug 2009 02:56:20 +0000 Received: from conversion-daemon.i-mtaout7.012.net.il by i-mtaout7.012.net.il (HyperSendmail v2007.08) id <0KP600L0059WG700@i-mtaout7.012.net.il> for gdb-patches@sourceware.org; Sun, 30 Aug 2009 05:56:17 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.144.38]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KP600A0M5HSDW40@i-mtaout7.012.net.il>; Sun, 30 Aug 2009 05:56:17 +0300 (IDT) Date: Sun, 30 Aug 2009 03:03:00 -0000 From: Eli Zaretskii Subject: Re: [RFA/RFC] Add dump and load command to process record and replay In-reply-to: <4A99909E.7030302@vmware.com> To: Michael Snyder Cc: teawater@gmail.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83ws4m9fhr.fsf@gnu.org> References: <4A91CEEC.5000802@vmware.com> <4A92D317.9010002@vmware.com> <4A948FF1.6000405@vmware.com> <4A949176.9060604@vmware.com> <831vmubitq.fsf@gnu.org> <83zl9i9xls.fsf@gnu.org> <4A99909E.7030302@vmware.com> 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/msg00553.txt.bz2 > Date: Sat, 29 Aug 2009 13:33:34 -0700 > From: Michael Snyder > CC: Hui Zhu , > "gdb-patches@sourceware.org" > > > Sorry, I don't understand: why would we want to have the record log in > > a core file? What am I missing here? > > Because the record-log itself does not record starting state -- > only changes of state. It is useless by itself if you don't > restore the starting state first. > > Hui's original patch used the "gcore" command to save the > starting state, and "target core" to restore it. > > The problem that I found with that was that it created two > independent files, core file and record-log file, and that > there was no way to assure ourselves (or the user) that the > two files corresponded to one another when they were re-loaded. > > That's why I suggested combining them into one file -- > in this implementation, by adding the record-log to an > extra section in the core file. Thanks for explaining. 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.