Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Process record and replay, 10/10
Date: Fri, 14 Nov 2008 16:29:00 -0000	[thread overview]
Message-ID: <daef60380811140553q7ca64726l7b7ae268dcdd7aa2@mail.gmail.com> (raw)
In-Reply-To: <uod0io7hl.fsf@gnu.org>

On Fri, Nov 14, 2008 at 19:46, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Tue, 11 Nov 2008 13:03:04 +0800
>> From: teawater <teawater@gmail.com>
>> Cc: gdb-patches@sourceware.org
>>
>> >> > By the way, I think we need a NEWS entry for this feature.
>> >> >
>> >>
>> >> What about add this:
>> >>
>> >> * Process record and replay
>> >>
>> >>   Record inferior execute log and replay it.
>> >
>> > OK, but I think at least one or two more sentences describing the
>> > feature would be nice.
>> >
>>
>> What about this:
>>
>> * Process record and replay
>>
>>   In a architecture environment that supports process record and
>>   replay, process record and replay target can record a log of the
>>   process execution, and replay it with both forward and reverse
>>   execute commands.
>
> This is fine, but please make 2 minor corrections:
>
>   In an architecture environment that supports process record and
>   replay, a ``process record and replay'' target can record a log of the
>   process execution, and replay it with both forward and reverse
>   execute commands.
>

OK. Thanks.

Hui


      reply	other threads:[~2008-11-14 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  7:53 teawater
2008-11-07 14:49 ` Eli Zaretskii
2008-11-08  4:40   ` teawater
2008-11-08  9:25     ` Eli Zaretskii
2008-11-11  5:43       ` teawater
2008-11-14 16:04         ` Eli Zaretskii
2008-11-14 16:29           ` teawater [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=daef60380811140553q7ca64726l7b7ae268dcdd7aa2@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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