[RFA, 4 of 3] save/restore process record, part 4 (docs and news)
Michael Snyder
msnyder@vmware.com
Sat Oct 17 22:25:00 GMT 2009
Eli Zaretskii wrote:
>> Date: Sat, 17 Oct 2009 12:05:27 -0700
>> From: Michael Snyder <msnyder@vmware.com>
>>
>> The fourth part of the trilogy. ;-)
>
> Thanks.
>
>> * docs/gdb.texinfo: Document record save/restore commands.
>
> This needs to state the name of the node where you made the changes.
OK
>> +* New commands
>> +
>> +record save <filename> -- Save a 'process record' execution log to a file.
>> +record restore <filename -- Restore an earlier 'process record' session.
>
> Please format these as we did with other new commands in NEWS.
Well, there's more than one format -- I'll use the most recent.
>> +Save the execution log of the inferior process into a modified core file.
>
> "Modified" is too overloaded. Suggest "specially formatted" instead.
OK.
>> +This execution log can then be debugged using the @code{process record}
>
> Well, you can't really "debug the execution log", can you? How about
>
> You can then replay this execution log as if you recorded it in this
> @value{GDBN} session.
All right. See attached.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: docsb.txt
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20091017/7954ca23/attachment.txt>
More information about the Gdb-patches
mailing list