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: Sat, 17 Oct 2009 20:16:00 -0000	[thread overview]
Message-ID: <83ljj9hj6n.fsf@gnu.org> (raw)
In-Reply-To: <4ADA1577.4000100@vmware.com>

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

?


  reply	other threads:[~2009-10-17 20:16 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 [this message]
2009-10-17 22:25   ` Michael Snyder
2009-10-18  4:08     ` Eli Zaretskii
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=83ljj9hj6n.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