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

> Date: Fri, 14 Nov 2008 23:40:22 +0800
> From: teawater <teawater@gmail.com>
> Cc: gdb-patches@sourceware.org
> 
> >> >> +               error (_("Process record: record stop the program."));
> >> >
> >> > Do you mean
> >> >
> >> >    Process record: program recording stopped.
> >> >
> >> > ?
> >>
> >> What about "Process record stop inferior."
> >
> > I'm not sure.  Can you explain what exactly does this message try to
> > say?  I will then suggest a better wording.
> 
> OK. When P record want make inferior stop. It will use this code.

Then I think

  error (_("Process record: inferior program stopped."));

> >> >> +  if (ret < 0)
> >> >> +    error (_("Process record record message error."));
> >> >
> >> > Do you mean something like "Process record error."?  That is, does
> >> > this happen when some error is encountered inside
> >> > gdbarch_process_record?
> >> >
> >>
> >> What about "Process record execute log error"?
> >
> > "Error executing process log record"?
> 
> What about "Process record target record execute log failed"?

I think "Process record: failed to record execution log" is better.


  reply	other threads:[~2008-11-14 18:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  7:47 teawater
2008-11-07 16:01 ` Eli Zaretskii
2008-11-11  4:20   ` teawater
2008-11-14 16:27     ` Eli Zaretskii
2008-11-14 17:29       ` teawater
2008-11-14 22:09         ` Eli Zaretskii [this message]
2008-11-15 19:02           ` 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=ufxlunoo7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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