From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] PR gdb/16304: Properly decode MODRM byte for 64-bit
Date: Sat, 14 Dec 2013 23:12:00 -0000 [thread overview]
Message-ID: <20131214231205.GB3792@gmail.com> (raw)
In-Reply-To: <CAMe9rOqgUCJ1Oab-Tug4tT6bsMTcUQnMHmKzs0hor5dUbHdYtw@mail.gmail.com>
On Sun, Dec 08, 2013 at 12:15:48PM -0800, H.J. Lu wrote:
> On Sun, Dec 8, 2013 at 11:56 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> > On Sun, Dec 8, 2013 at 11:43 AM, H.J. Lu <hongjiu.lu@intel.com> wrote:
> >> 64-bit mode doesn't have 16-bit address. This patch fixes it. Tested on
> >> Linux/x86-64. OK to install?
> >>
> >> H.J.
> >> --
> >> 2013-12-08 H.J. Lu <hongjiu.lu@intel.com>
> >>
> >> PR gdb/16304
> >> * i386-tdep.c (i386_record_lea_modrm_addr): Don't use 16-bit
> >> address in 64-bit mode.
> >> ---
> >> gdb/i386-tdep.c | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/gdb/i386-tdep.c b/gdb/i386-tdep.c
> >> index 597d672..4a91d80 100644
> >> --- a/gdb/i386-tdep.c
> >> +++ b/gdb/i386-tdep.c
> >> @@ -4192,9 +4192,9 @@ i386_record_lea_modrm_addr (struct i386_record_s *irp, uint64_t *addr)
> >> ULONGEST offset64;
> >>
> >> *addr = 0;
> >> - if (irp->aflag)
> >> + if (irp->aflag || gdbarch_bfd_arch_info (gdbarch)->bits_per_word == 64)
> >> {
> >
> > We seem to check ir.regmap[X86_RECORD_R8_REGNUM] for
> > 64-bit target. I will try that.
> >
>
> This works. OK to install?
>
> Thanks.
>
> --
> H.J.
> ---
> 2013-12-08 H.J. Lu <hongjiu.lu@intel.com>
>
> PR gdb/16304
> * i386-tdep.c (i386_record_lea_modrm_addr): Don't use 16-bit
> address in 64-bit mode.
>
> ---
> gdb/i386-tdep.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/i386-tdep.c b/gdb/i386-tdep.c
> index 597d672..fee58c3 100644
> --- a/gdb/i386-tdep.c
> +++ b/gdb/i386-tdep.c
> @@ -4192,9 +4192,9 @@ i386_record_lea_modrm_addr (struct i386_record_s
> *irp, uint64_t *addr)
> ULONGEST offset64;
>
> *addr = 0;
> - if (irp->aflag)
> + if (irp->aflag || irp->regmap[X86_RECORD_R8_REGNUM])
> {
> - /* 32 bits */
> + /* 32/64 bits */
> int havesib = 0;
> uint8_t scale = 0;
> uint8_t byte;
Hi Mark,
Do you get time to review this?
Thanks.
H.J.
prev parent reply other threads:[~2013-12-14 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 19:44 H.J. Lu
2013-12-08 19:56 ` H.J. Lu
2013-12-08 20:15 ` H.J. Lu
2013-12-14 23:12 ` H.J. Lu [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=20131214231205.GB3792@gmail.com \
--to=hjl.tools@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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