Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: palves@redhat.com, yao@codesourcery.com, hjl.tools@gmail.com,
	       binutils@sourceware.org, gdb@sourceware.org
Subject: Re: [rfc] bi-arch for x86-64 corefile.
Date: Tue, 30 Oct 2012 14:53:00 -0000	[thread overview]
Message-ID: <508FE9EA.1090709@redhat.com> (raw)
In-Reply-To: <201210301354.q9UDseOZ022173@glazunov.sibelius.xs4all.nl>

On 10/30/2012 01:54 PM, Mark Kettenis wrote:

> The problem is that the Linux core file support in bfd is still relies
> on native headers.  Trying to "fix them up" for bi-arch like what's been
> done for the last couple of years on Linux is never going to give you
> true cross-debugging support.

I agree.  The core files' layout is ABI, so we should not need, and should
not rely on host headers for generating core files.  Given that gcore
works with gdbserver too, a non-x86 hosted GDB debugging against
a x86 gdbserver should be able to generate x86 core files, without
x86 target headers present when building the non-x86 gdb/bfd.
I very much support that direction.

The patch looks to me a a small step in the right direction,
in that we rely a little bit less on the host headers though.
I don't know what structures and constants we're still picking up
from host headers.

Regardless, that's independent of the --enable-64-bit-bfd vs
--enable-targets=x86_64-pc-linux-gnu issue, which seems like
H.J has just fixed.  Thanks!

-- 
Pedro Alves


  reply	other threads:[~2012-10-30 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1350881426-4945-1-git-send-email-yao@codesourcery.com>
     [not found] ` <CAMe9rOpeR8AX6EG8mNcfZNHNMrpZmv1S4O8H7BmREsU1vyN1jQ@mail.gmail.com>
     [not found]   ` <508F3B88.8060701@codesourcery.com>
     [not found]     ` <CAMe9rOrXFG_E7F0hhHjexEhahWWNVwfxfSXoOcCAU9XotSuuVw@mail.gmail.com>
     [not found]       ` <508F578F.8050807@codesourcery.com>
     [not found]         ` <CAMe9rOp_7=S5rTEC+T8Q-UkZj3wDNNM6AhwbRXn18nZAGDH03A@mail.gmail.com>
2012-10-30 12:37           ` Yao Qi
2012-10-30 12:58             ` Pedro Alves
2012-10-30 13:55               ` Mark Kettenis
2012-10-30 14:53                 ` Pedro Alves [this message]
2012-10-30 13:32             ` H.J. Lu

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=508FE9EA.1090709@redhat.com \
    --to=palves@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=yao@codesourcery.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