Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Alan Modra <amodra@gmail.com>, Binutils <binutils@sourceware.org>,
	       GDB <gdb-patches@sourceware.org>
Subject: Re: Use elfcore_write_linux_prstatus in gdb
Date: Thu, 21 Jan 2016 14:26:00 -0000	[thread overview]
Message-ID: <56A0EA83.3040403@redhat.com> (raw)
In-Reply-To: <CAMe9rOoYJcX6WODb-e8jLPOzK6hE7KhYcPyuV91SjWe1A-8y=w@mail.gmail.com>

On 01/21/2016 02:17 PM, H.J. Lu wrote:
> On Thu, Jan 21, 2016 at 6:05 AM, Pedro Alves <palves@redhat.com> wrote:
>> On 01/21/2016 01:24 PM, H.J. Lu wrote:

>>> Please take a look at bfd/hosts/x86-64linux.h to see how to dump core
>>> x86-64.
>>
>> I don't have x32 setup on my machine.  AFAICS, elf_prstatusx32 is exactly
>> like elf_prstatus32, except it takes a 64-bit regset.
...

>>
>> elfcore_write_linux_prstatus32 should be reached.  Other than that,
>> I have no idea (other than installing the stop gap on x32 too).
>>
> 
> x32 has different core types (core layout) from m32 and m64.
> See bfd/hosts/x86-64linux.h for details.  

As I said, "AFAICS, elf_prstatusx32 is exactly like elf_prstatus32,
except it takes a 64-bit regset."  It's probably an issue
of alignment/padding?

> You need
> elfcore_write_linux_prstatusx32 or change
> elfcore_write_linux_prstatus32 to suport x32.

I really can't be working further on this myself right now, sorry.

I've updated the branch to install the stop-gap on x32 as well, which
really ends up calling the same function we call today.
Please give it a try.

Thanks,
Pedro Alves


  reply	other threads:[~2016-01-21 14:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  9:29 Alan Modra
2016-01-21 12:25 ` Pedro Alves
2016-01-21 13:11   ` Pedro Alves
2016-01-21 13:24     ` H.J. Lu
2016-01-21 14:05       ` Pedro Alves
2016-01-21 14:17         ` H.J. Lu
2016-01-21 14:26           ` Pedro Alves [this message]
2016-01-21 14:33             ` H.J. Lu
2016-01-21 14:44             ` Alan Modra
2016-01-21 15:59             ` H.J. Lu
2016-01-21 16:02               ` Pedro Alves

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=56A0EA83.3040403@redhat.com \
    --to=palves@redhat.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.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