From: Hui Zhu <teawater@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFC: move agent opcodes to common file
Date: Mon, 21 Feb 2011 08:17:00 -0000 [thread overview]
Message-ID: <AANLkTimWb_OSTKLtvN26N0uinGrO1Dbwc8_0YxgmBW0=@mail.gmail.com> (raw)
In-Reply-To: <201102202134.00239.pedro@codesourcery.com>
On Mon, Feb 21, 2011 at 05:33, Pedro Alves <pedro@codesourcery.com> wrote:
> On Sunday 20 February 2011 06:23:18, Hui Zhu wrote:
>> But when I try to add 0x31 to ax.def, I got some build error with gdbserver:
> ...
>
>> DEFOP (invalid2, 0, 0, 0, 0, 0x2f)
>
> I think that 0x2f here is a pasto and should have been 0x31, so
> you probably want to replace it with your opcode, not add a new
> entry.
>
> --
> Pedro Alves
>
Cool. My part is OK. Thanks for your help Pedro.
Tom, leave op 31 must waste a lot of time. Thanks a lot.
Best,
Hui
prev parent reply other threads:[~2011-02-21 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 22:25 Tom Tromey
2011-02-16 23:33 ` Hui Zhu
2011-02-17 2:06 ` Hui Zhu
2011-02-17 15:13 ` Tom Tromey
2011-02-18 19:11 ` Pedro Alves
2011-02-18 23:35 ` Tom Tromey
2011-02-20 15:06 ` Hui Zhu
2011-02-20 21:47 ` Pedro Alves
2011-02-21 8:17 ` 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='AANLkTimWb_OSTKLtvN26N0uinGrO1Dbwc8_0YxgmBW0=@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.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