From: Eli Zaretskii <eliz@gnu.org>
To: teawater <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Process record and replay, 8/10
Date: Fri, 07 Nov 2008 15:34:00 -0000 [thread overview]
Message-ID: <uljvvsg85.fsf@gnu.org> (raw)
In-Reply-To: <daef60380811052350v3232a91ep6241e687f2f18be@mail.gmail.com>
> Date: Thu, 6 Nov 2008 15:50:44 +0800
> From: teawater <teawater@gmail.com>
>
> This patch add code to make I386 architecture support process record and replay.
Thanks.
> + printf_unfiltered (_("Process record: read memeory 0x%s error.\n"),
^^^^^^^
A typo. (There are several more like it.)
Also, I suggest to say "error 0x%s", not "0x%s error". The latter is
confusing for the ears of an English speaker, I think.
> + /* XXX: index == 4 is always invalid */
Why the XXX in this comment?
> + /* arith & logic */
> + case 0x00 ... 0x05:
> + case 0x08 ... 0x0d:
> + case 0x10 ... 0x15:
> + case 0x18 ... 0x1d:
> + case 0x20 ... 0x25:
> + case 0x28 ... 0x2d:
> + case 0x30 ... 0x35:
> + case 0x38 ... 0x3d:
Is this valid ISO C?
> + if (record_debug)
> + printf_unfiltered (_
> + ("Process record ignores the memory change of instruction in address 0x%s because it can't get the value of the segment register.\n"),
^^^^^^^^^^
"at address".
By the way, do we need debug messages to be translatable? Other
similar places in the patches don't have them in _().
> + case 0x9b:
> + printf_unfiltered (_
> + ("Process record don't support instruction fwait.\n"));
^^^^^^^^^^^^^
"doesn't support"
By the way, what happens if the code stream includes one of these
``unsupported'' instructions? What will the user see at replay time?
next prev parent reply other threads:[~2008-11-07 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 7:51 teawater
2008-11-06 17:40 ` Doug Evans
2008-11-07 2:02 ` teawater
2008-11-07 15:34 ` Eli Zaretskii [this message]
2008-11-10 14:41 ` teawater
2008-11-10 14:51 ` Andreas Schwab
2008-11-10 17:45 ` teawater
2008-11-14 16:28 ` Eli Zaretskii
2008-11-14 17:18 ` teawater
2008-11-07 18:43 ` Marc Khouzam
2008-11-07 19:03 ` Michael Snyder
2008-11-10 14:42 ` 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=uljvvsg85.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