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: Sun, 18 Oct 2009 06:05:51 +0200
- Subject: Re: [RFA, 4 of 3] save/restore process record, part 4 (docs and news)
- References: <4ADA1577.4000100@vmware.com> <83ljj9hj6n.fsf@gnu.org> <4ADA430C.9080502@vmware.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 17 Oct 2009 15:19:56 -0700
> From: Michael Snyder <msnyder@vmware.com>
>
> +* New commands
> +
> +record save (filename)
> + Save a 'process record' execution log to a file.
> +record restore (filename)
> + Restore an earlier 'process record' session.
> +
This is okay.
> +@kindex record save
> +@kindex rec save
> +@item record save [@var{file}]
> +@itemx rec save [@var{file}]
> +Save the execution log of the inferior process into a modified core file.
> +The optional argument @var{file} specifies the file name in which to
> +save the execution log. If not specified, the file name defaults
> +to @file{gdb_record.@var{pid}}, where @var{pid} is is the PID of the
> +inferior process.
> +
> +@kindex record restore
> +@kindex rec restore
> +@item record restore [@var{file}]
> +@itemx rec restore [@var{file}]
> +Restore the execution log of an earlier session from the file @var{file}
> +(required), which has been created using the command @code{record save}.
> +This execution log can then be debugged using the @code{process record}
> +target, in replay mode, just like replaying a live debugging session.
Looks like you sent a wrong patch, since this is unchanged from the
original version.