This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


> Date: Wed, 15 Oct 2008 15:33:53 +0800
> From: teawater <teawater@gmail.com>
> 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''?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]