Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: gdb-patches@sourceware.org, teawater@gmail.com
Subject: Re: [RFA, 4 of 3] save/restore process record, part 4 (docs and news)
Date: Sun, 18 Oct 2009 04:08:00 -0000	[thread overview]
Message-ID: <83iqedgxcw.fsf@gnu.org> (raw)
In-Reply-To: <4ADA430C.9080502@vmware.com>

> 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.


  reply	other threads:[~2009-10-18  4:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-17 19:11 Michael Snyder
2009-10-17 20:16 ` Eli Zaretskii
2009-10-17 22:25   ` Michael Snyder
2009-10-18  4:08     ` Eli Zaretskii [this message]
2009-10-18  4:13       ` Michael Snyder
2009-10-18 18:37         ` Eli Zaretskii
2009-10-22 19:42           ` Michael Snyder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83iqedgxcw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox