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


On Thu, Oct 16, 2008 at 03:43, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 15 Oct 2008 11:48:53 -0700
>> From: Michael Snyder <msnyder@vmware.com>
>> CC: teawater <teawater@gmail.com>,
>>  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>>
>> Eli, I think the relation is that we will save one log entry
>> for each instruction executed.  Not necessarily that we save
>> the instruction itself, but since we do save the PC (it being
>> part of the state that is changed by executing the instruction),
>> we always have access to the instruction itself if we want it
>> (either in memory or in object file).
>
> I understand that (now).  But the original text, viz.
>
>  When this target is in use, if the next instruction to be executed
>  is in the execution log, ...
>  ^^^^^^^^^^^^^^^^^^^^^^^
>
> made it sound like the instructions themselves are in the log.  This
> will need to be rephrased.
>

Sorry for understand your mean so slow.

How about change it to "if the next instruction has the execution log for it"?


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