From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4445 invoked by alias); 15 Oct 2008 08:41:24 -0000 Received: (qmail 4431 invoked by uid 22791); 15 Oct 2008 08:41:23 -0000 X-Spam-Check-By: sourceware.org Received: from ti-out-0910.google.com (HELO ti-out-0910.google.com) (209.85.142.190) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 15 Oct 2008 08:40:48 +0000 Received: by ti-out-0910.google.com with SMTP id d10so1701339tib.12 for ; Wed, 15 Oct 2008 01:40:45 -0700 (PDT) Received: by 10.110.37.3 with SMTP id k3mr550933tik.13.1224060044832; Wed, 15 Oct 2008 01:40:44 -0700 (PDT) Received: by 10.110.42.9 with HTTP; Wed, 15 Oct 2008 01:40:44 -0700 (PDT) Message-ID: Date: Wed, 15 Oct 2008 08:41:00 -0000 From: teawater To: "Eli Zaretskii" Subject: Re: [reverse RFC] Add documentation for process record and replay Cc: gdb-patches@sourceware.org, msnyder@vmware.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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/msg00367.txt.bz2 On Wed, Oct 15, 2008 at 16:14, Eli Zaretskii wrote: >> 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''? > OK. For example, x86 instruction "nop". It not change anything except $eip (x86 pc reg). Then, record $eip current value. That's all.