Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: PR corefiles/11511: gcore doesn't work with orig_rax on  	Linux/amd64
Date: Sat, 17 Apr 2010 18:50:00 -0000	[thread overview]
Message-ID: <z2q6dc9ffc81004171150z164a5fb2y727e835914421f6b@mail.gmail.com> (raw)
In-Reply-To: <201004171625.o3HGPc93029549@glazunov.sibelius.xs4all.nl>

On Sat, Apr 17, 2010 at 9:25 AM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> Date: Sat, 17 Apr 2010 09:11:15 -0700
>> From: "H.J. Lu" <hongjiu.lu@intel.com>
>>
>> This patch adds orig_rax support to amd64_linux_gregset_reg_offset.
>> amd64 has both tdep->gregset_reg_offset/tdep->gregset_num_regs and
>> amd64_native_gregset64_reg_offset/amd64_native_gregset64_num_regs.  They
>> are identical. There is no need to keep both.  This patch also removes
>> amd64_native_gregset64_reg_offset/amd64_native_gregset64_num_regs. OK
>> to install?
>
> No.  I want to keep the -nat.c and -tdep.c code separate.

Can I replace amd64_linux_gregset64_reg_offset with
amd64_linux_gregset_reg_offset, like amd64nbsd-nat.c
and amd64obsd-nat.c?

Thanks.

H.J.
--
> The bit below is ok, but please drop the other bits.
>
>>       * amd64-linux-tdep.c (amd64_linux_gregset_reg_offset): Support
>>       orig_rax.
>
>> diff --git a/gdb/amd64-linux-tdep.c b/gdb/amd64-linux-tdep.c
>> index 1205e31..f249d5d 100644
>> --- a/gdb/amd64-linux-tdep.c
>> +++ b/gdb/amd64-linux-tdep.c
>> @@ -87,7 +87,14 @@ static int amd64_linux_gregset_reg_offset[] =
>>    23 * 8,                    /* %ds */
>>    24 * 8,                    /* %es */
>>    25 * 8,                    /* %fs */
>> -  26 * 8                     /* %gs */
>> +  26 * 8,                    /* %gs */
>> +  -1, -1, -1, -1, -1, -1, -1, -1,
>> +  -1, -1, -1, -1, -1, -1, -1, -1,
>> +  -1, -1, -1, -1, -1, -1, -1, -1,
>> +  -1, -1, -1, -1, -1, -1, -1, -1, -1,
>> +  -1, -1, -1, -1, -1, -1, -1, -1,
>> +  -1, -1, -1, -1, -1, -1, -1, -1,
>> +  15 * 8                     /* "orig_rax" */
>>  };
>>
>>
>



-- 
H.J.


  reply	other threads:[~2010-04-17 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 16:11 H.J. Lu
2010-04-17 16:25 ` Mark Kettenis
2010-04-17 18:50   ` H.J. Lu [this message]
2010-04-18 21:33     ` Mark Kettenis
2010-04-19 15:26       ` Daniel Jacobowitz
2010-04-19 17:21       ` H.J. Lu
2010-04-19 17:28         ` H. Peter Anvin
2010-04-20 22:17           ` Roland McGrath

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=z2q6dc9ffc81004171150z164a5fb2y727e835914421f6b@mail.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