This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA, 4 of 3] save/restore process record, part 4 (docs and news)
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Michael Snyder <msnyder at vmware dot com>
- Cc: gdb-patches at sourceware dot org, teawater at gmail dot com
- Date: Sat, 17 Oct 2009 22:14:24 +0200
- Subject: Re: [RFA, 4 of 3] save/restore process record, part 4 (docs and news)
- References: <4ADA1577.4000100@vmware.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.
> +* 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.
> +Save the execution log of the inferior process into a modified core file.
"Modified" is too overloaded. Suggest "specially formatted" instead.
> +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.
?