Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, msnyder@vmware.com
Subject: Re: [PATCH] Fix cygwin build error with i386-linux-tdep.c
Date: Sun, 30 Aug 2009 15:00:00 -0000	[thread overview]
Message-ID: <daef60380908300737k239bf7dcp6b4eb99c3b23b6f6@mail.gmail.com> (raw)
In-Reply-To: <daef60380908300709i382261c9w6152a694dcdb5975@mail.gmail.com>

On Sun, Aug 30, 2009 at 22:09, Hui Zhu<teawater@gmail.com> wrote:
> On Sun, Aug 30, 2009 at 21:56, Mark Kettenis<mark.kettenis@xs4all.nl> wrote:
>>> From: Hui Zhu <teawater@gmail.com>
>>> Date: Sun, 30 Aug 2009 21:15:22 +0800
>>>
>>> 2009-08-29  Hui Zhu  <teawater@gmail.com>
>>>
>>>       * i386-linux-tdep.c (i386_linux_intx80_sysenter_record): Add
>>>       (unsigned) before tmpu32.
>>
>> Ugh!  Casts like that are ugly.
>>
>> This made me look at the code again and realize that what you're doing
>> in that function is wrong.  You should be using
>> regcache_{raw|cooked}_read_unsigned() instead of regcache_raw_read().
>> Then the whole issue of printing an uint32_t goes away.  When you do
>> change the code like that please use a more meaningful variable name
>> instead of 'tmpu32'.  My suggestion would be 'syscall'.
>
> For the regcache_raw_read_unsigned, I am not agres with it.
>
> void
> regcache_raw_read_unsigned (struct regcache *regcache, int regnum,
>                            ULONGEST *val)
> {
>  gdb_byte *buf;
>  gdb_assert (regcache != NULL);
>  gdb_assert (regnum >= 0 && regnum < regcache->descr->nr_raw_registers);
>  buf = alloca (regcache->descr->sizeof_register[regnum]);
>  regcache_raw_read (regcache, regnum, buf);
>  (*val) = extract_unsigned_integer
>             (buf, regcache->descr->sizeof_register[regnum],
>              gdbarch_byte_order (regcache->descr->gdbarch));
> }
>
> It just add a "extract_unsigned_integer".  For this code, it in
> i386-linux-tdep.c.  We know that I386_EAX_REGNUM is 32 bits.  So we
> don't need extract_unsigned_integer to set anything.
>
> Thanks,
> Hui

Oops, I forget that we have the byte order trouble.  Thanks for remind
me.  I will fix it.

Thanks,
Hui

>
>>
>> Cheers,
>>
>> Mark
>>
>>> Index: gdb/i386-linux-tdep.c
>>> ===================================================================
>>> --- gdb.orig/i386-linux-tdep.c        2009-08-23 21:17:37.000000000 +0800
>>> +++ gdb/i386-linux-tdep.c     2009-08-30 20:19:53.828125000 +0800
>>> @@ -374,7 +374,7 @@
>>>    if (tmpu32 > 499)
>>>      {
>>>        printf_unfiltered (_("Process record and replay target doesn't "
>>> -                           "support syscall number %u\n"), tmpu32);
>>> +                           "support syscall number %u\n"), (unsigned) tmpu32);
>>>        return -1;
>>>      }
>>>
>>
>


  reply	other threads:[~2009-08-30 14:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 13:56 Hui Zhu
2009-08-30 14:09 ` Mark Kettenis
2009-08-30 14:20   ` Hui Zhu
2009-08-30 15:00     ` Hui Zhu [this message]
2009-08-31  8:46       ` Hui Zhu
2009-08-31  8:49         ` Jiang Jilin
2009-08-31 12:05           ` Hui Zhu
2009-08-31 16:33             ` Mark Kettenis
2009-09-01  2:15               ` Hui Zhu
2009-09-05 20:34         ` Michael Snyder
2009-09-05 21:15           ` Joel Brobecker
2009-09-06  4:15             ` Hui Zhu
2009-09-09  2:22               ` Hui Zhu
2009-09-09  3:31                 ` Michael Snyder
2009-09-09  5:59                   ` Hui Zhu
2009-08-30 14:37   ` Andreas Schwab
2009-08-30 15:14     ` Hui Zhu
2009-08-30 15:22 ` Jiang Jilin
2009-08-30 18:00   ` Hui Zhu
2009-08-30 23:43     ` Jiang Jilin
2009-08-30 23:53       ` Hui Zhu
2009-08-31  0:32         ` Jiang Jilin
2009-08-31  2:52           ` Jiang Jilin

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=daef60380908300737k239bf7dcp6b4eb99c3b23b6f6@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --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