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: Tue, 11 Nov 2008 05:43:00 -0000 [thread overview]
Message-ID: <daef60380811102103l77922ea9g614bc6287b778a7f@mail.gmail.com> (raw)
In-Reply-To: <ubpwqsh9r.fsf@gnu.org>
Thanks Eli.
On Sat, Nov 8, 2008 at 17:23, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sat, 8 Nov 2008 12:39:44 +0800
>> From: teawater <teawater@gmail.com>
>> Cc: gdb-patches@sourceware.org
>>
>> >> +@chapter Recording programs running message and replay it
>> >
>> > I don't understand this phrase. What did you want to say? what does
>> > the word "message" have to do with this feature?
>>
>> What about "Recording inferior execute log and replay it"?
>
> If this is the intent, then I suggest simply
>
> Recording inferior's execution and replaying it
>
> (The fact that you record execution log is an implementation detail,
> and certainly does not need to be stated in the chapter's name.)
>
OK. I will use it.
>> > Is the command "target record" or just "record"? or is the latter an
>> > alias of the former? We need to explain all this in the manual,
>> > because the @item says "target record", while in the last sentence
>> > above you say that the command is "record"
>>
>> "target record" is the real command.
>> "record" is a command call "target record". I want it to be the alias
>> of "target record"
>> "rec" is a alias of "record".
>
> The aliases should be described in the manual.
OK. I will.
>
>> What about change "@code{record}" to "@code{target record}"?
>
> Fine with me.
>
>> > 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.
next prev parent reply other threads:[~2008-11-11 5:03 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 [this message]
2008-11-14 16:04 ` Eli Zaretskii
2008-11-14 16:29 ` teawater
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=daef60380811102103l77922ea9g614bc6287b778a7f@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