Re: [reverse RFC] Add documentation for process record and replay

teawater
2008-10-15T07:34:31Z

On Wed, Oct 15, 2008 at 15:21, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 15 Oct 2008 13:50:30 +0800
>> From: teawater <teawater@gmail.com>
>> 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.