Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] NEWS: mention record save/restore
Date: Tue, 03 Nov 2009 06:19:00 -0000	[thread overview]
Message-ID: <daef60380911022219h616b2048kb71e2bc3f6de21d@mail.gmail.com> (raw)
In-Reply-To: <4AEDFC59.80402@vmware.com>

Cool.

Thanks,
Hui

On Mon, Nov 2, 2009 at 05:23, Michael Snyder <msnyder@vmware.com> wrote:
> Eli Zaretskii wrote:
>>>
>>> Date: Sun, 01 Nov 2009 12:55:34 -0800
>>> From: Michael Snyder <msnyder@vmware.com>
>>>
>>> 2009-11-01  Michael Snyder  <msnyder@vmware.com>
>>>
>>>        * NEWS (New Commands): Mention record save/restore.
>>>
>>> Index: NEWS
>>> ===================================================================
>>> RCS file: /cvs/src/src/gdb/NEWS,v
>>> retrieving revision 1.336
>>> diff -u -p -r1.336 NEWS
>>> --- NEWS        28 Oct 2009 15:01:27 -0000      1.336
>>> +++ NEWS        1 Nov 2009 20:54:26 -0000
>>> @@ -24,6 +24,14 @@ Xilinx MicroBlaze            microblaze
>>>   * New commands (for set/show, see "New options" below)
>>>  +record save [<FILENAME>]
>>> +  Save a file (in core file format) containing the process record +
>>>  execution log for replay debugging at a later time.
>>> +
>>> +record restore <FILENAME>
>>> +  Restore the process record execution log that was saved at an
>>> +  earlier time, for replay debugging.
>>> +
>>>  add-inferior [-copies <N>] [-exec <FILENAME>]
>>>   Add a new inferior.
>>
>> This is fine, thanks.
>
> Committed.
>


      reply	other threads:[~2009-11-03  6:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 20:55 Michael Snyder
2009-11-01 21:19 ` Eli Zaretskii
2009-11-01 21:23   ` Michael Snyder
2009-11-03  6:19     ` Hui Zhu [this message]

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=daef60380911022219h616b2048kb71e2bc3f6de21d@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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