From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Bug in i386_process_record
Date: Tue, 18 Aug 2009 09:22:00 -0000 [thread overview]
Message-ID: <daef60380908180210r280bf835laa7569042e6a5458@mail.gmail.com> (raw)
In-Reply-To: <daef60380908180206r1f749c61t583d2bf2bb1f8b6a@mail.gmail.com>
About rex in i386:
case 0x40:
case 0x41:
case 0x42:
case 0x43:
case 0x44:
case 0x45:
case 0x46:
case 0x47:
case 0x48:
case 0x49:
case 0x4a:
case 0x4b:
case 0x4c:
case 0x4d:
case 0x4e:
case 0x4f:
if (ir.regmap[X86_RECORD_R8_REGNUM])
{
Only in amd64, ir.regmap[X86_RECORD_R8_REGNUM] is true, so it will not
affect 32bits.
Thanks,
Hui
On Tue, Aug 18, 2009 at 17:06, Hui Zhu<teawater@gmail.com> wrote:
> I tried. Everything is OK.
>
> Thanks,
> Hui
>
> On Tue, Aug 18, 2009 at 07:01, Hui Zhu<teawater@gmail.com> wrote:
>> On Tue, Aug 18, 2009 at 02:24, Michael Snyder<msnyder@vmware.com> wrote:
>>> Hui Zhu wrote:
>>>
>>>> (gdb) FAIL: gdb.reverse/machinestate.exp: step
>>>>
>>>> I think the fail is because rs didn't step into hide.
>>>
>>> 32bit or 64?
>>> If 64, did you try it after applying my two recent patches?
>>>
>>> Anyway, that is not the only reason it fails.
>>> It fails for me on 32 bit intel.
>>
>> I try amd64 with your new patch in last night, everything is OK.
>>
>> For x86, I try it in prev some day, everything is OK too.
>>
>> This pc don't have the gdb-cvs-head and I cannot connect gdb cvs now.
>> I will try it later.
>>
>> Thanks,
>> Hui
>>
>
next prev parent reply other threads:[~2009-08-18 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 12:45 Michael Snyder
2009-08-16 18:55 ` Hui Zhu
2009-08-17 6:36 ` Hui Zhu
2009-08-17 14:37 ` Hui Zhu
2009-08-17 18:34 ` Michael Snyder
2009-08-18 3:03 ` Hui Zhu
2009-08-18 9:11 ` Hui Zhu
2009-08-18 9:22 ` Hui Zhu [this message]
2009-08-17 18:17 ` Michael Snyder
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=daef60380908180210r280bf835laa7569042e6a5458@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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