From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13081 invoked by alias); 15 Oct 2008 07:34:31 -0000 Received: (qmail 13072 invoked by uid 22791); 15 Oct 2008 07:34:31 -0000 X-Spam-Check-By: sourceware.org Received: from ti-out-0910.google.com (HELO ti-out-0910.google.com) (209.85.142.189) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 15 Oct 2008 07:33:56 +0000 Received: by ti-out-0910.google.com with SMTP id d10so1676863tib.12 for ; Wed, 15 Oct 2008 00:33:53 -0700 (PDT) Received: by 10.110.47.9 with SMTP id u9mr465690tiu.42.1224056033230; Wed, 15 Oct 2008 00:33:53 -0700 (PDT) Received: by 10.110.42.9 with HTTP; Wed, 15 Oct 2008 00:33:53 -0700 (PDT) Message-ID: Date: Wed, 15 Oct 2008 07:34: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/msg00363.txt.bz2 On Wed, Oct 15, 2008 at 15:21, Eli Zaretskii wrote: >> Date: Wed, 15 Oct 2008 13:50:30 +0800 >> From: teawater >> Cc: gdb-patches@sourceware.org, msnyder@vmware.com >> >> >> +When this target is in use, if the next instruction to be executed is in the >> >> +execution log, @value{GDBN} will debug in replay mode so that all the >> >> +execution events are taken from the execution log. Otherwise, @value{GDBN} >> >> +will debug in record mode and record the execution log while executing >> >> +normally. >> > >> > What exactly is the "execution log"? You talk about "next >> > instruction", which seems to hint that the log records the machine >> > instructions executed by the inferior -- is that true? If so, what >> > are the "execution events" you mention here -- are they just a synonym >> > for the "instructions", or are they something else? >> > >> >> "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.