From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
binutils@sourceware.org,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [rfc] bi-arch for x86-64 corefile.
Date: Tue, 30 Oct 2012 12:58:00 -0000 [thread overview]
Message-ID: <508FCEC5.2020403@redhat.com> (raw)
In-Reply-To: <508FCA04.6010600@codesourcery.com>
On 10/30/2012 12:37 PM, Yao Qi wrote:
> This requires something different in configure options. In my previous patch, when configure i686-pc-linux-gnu-gdb to handle bi-arch, we run configure with '--enable-64-bit-bfd'. In current trunk (w/ your patch), we have to run configure with '--enable-targets=x86_64-pc-linux-gnu'.
>
> Copy gdb@ here to make sure GDB people are aware of this change, otherwise, configuring gdb with '--enable-64-bit-bfd' only still doesn't work for handling x86-64 corefile on x86 gdb.
That sounds like an unnecessary restriction. A 32-bit GDB can debug a 64-bit
inferior with gdbserver just fine (it can also debug a 64-bit core), provided GDB
is built with --enable-64-bit-bfd. Yes, debugging a native 64-bit inferior won't
work due to ptrace limitations, but GDB's gcore command can generate cores
even when remote debugging w/ gdbserver.
We have things like this, gdb/configure.tgt:
i[34567]86-*-linux*)
# Target: Intel 386 running GNU/Linux
gdb_target_obs="i386-tdep.o i386-linux-tdep.o glibc-tdep.o i387-tdep.o \
solib-svr4.o symfile-mem.o \
linux-tdep.o linux-record.o"
if test "x$enable_64_bit_bfd" = "xyes"; then
# Target: GNU/Linux x86-64
gdb_target_obs="amd64-tdep.o amd64-linux-tdep.o ${gdb_target_obs}"
fi
build_gdbserver=yes
;;
So it's be nice if bfd did the same in this case. Thus, I'd very much
prefer if --enable-64-bit-bfd was enough for making bi-arch corefiles
work.
--
Pedro Alves
next prev parent reply other threads:[~2012-10-30 12:58 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 [this message]
2012-10-30 13:55 ` Mark Kettenis
2012-10-30 14:53 ` Pedro Alves
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=508FCEC5.2020403@redhat.com \
--to=palves@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).