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

[teawater <teawater@gmail.com>]

On Fri, Oct 17, 2008 at 18:06, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 17 Oct 2008 11:17:59 +0800
>> From: teawater <teawater@gmail.com>
>> Cc: msnyder@vmware.com, gdb-patches@sourceware.org
>>
>> Thanks Eli.
>> I make a new one.
>
> Almost there ;-)
>
>> > I'm somewhat concerned about the fact that the functionality and
>> > limitations of the ``record and replay'' target are not described at
>> > all.  If I were to debug using such an architecture, I'd like to know
>> > what it can and cannot do.  For example, if I replay, does the I/O
>> > happen like it happened during the recorded session?  What about
>> > signals? crashes? etc.  Are there things that simply cannot be
>> > reproduced exactly, due to fundamental limitations of the replay
>> > target?
>
> Do you have an opinion about these concerns?


I had added some introduce after "@cindex recording programs running
message and replay it".

When this target is in use, if the execution log includes the record for
the next instruction, @value{GDBN} will debug in replay mode.  So inferior
will not really execute and all the execution events are taken from the
execution log.  Just the values of registers (include pc register) and
memory of the inferior will be changed.

>
>> +Stop process record and replay target at once. When Process record and
>                                                ^^
> Still one space.
>
>> +earlier point), the inferior process will become ``live" at that earlier state,
>
> ``live'', not ``live".  (There are more cases of this in the text.)
>

Thanks, I will fix them.