From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24890 invoked by alias); 15 Oct 2008 08:15:13 -0000 Received: (qmail 24841 invoked by uid 22791); 15 Oct 2008 08:15:12 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout1.012.net.il (HELO mtaout1.012.net.il) (84.95.2.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 15 Oct 2008 08:14:22 +0000 Received: from HOME-C4E4A596F7 ([77.127.24.3]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K8R001GCTM47N10@i-mtaout1.012.net.il> for gdb-patches@sourceware.org; Wed, 15 Oct 2008 10:15:41 +0200 (IST) Date: Wed, 15 Oct 2008 08:15:00 -0000 From: Eli Zaretskii Subject: Re: [reverse RFC] Add documentation for process record and replay In-reply-to: X-012-Sender: halo1@inter.net.il To: teawater Cc: gdb-patches@sourceware.org, msnyder@vmware.com Reply-to: Eli Zaretskii Message-id: References: 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: 2008-10/txt/msg00366.txt.bz2 > Date: Wed, 15 Oct 2008 15:33:53 +0800 > From: teawater > Cc: gdb-patches@sourceware.org, msnyder@vmware.com > > >> "execution log" mean is before a instruction execute, record the > >> values of register and memory that will be change in this instruction > >> to a list. > > > > So you record the values of registers and memory AND the instruction? > > The frequent use of ``instruction'' and ``insn'' is a clear hint to > > this; if as a matter of fact the instructions are not recorded, we > > should modify the text to eliminate those hints. > > > > No, it just record the values of registers and memory, not care about > instruction. Then I think it's really confusing to talk about ``instructions'' in this context. At the very least, we should explain what we mean by ``instructions'' in that section. Can you show me a few examples of the recorded ``instructions''?