From: Pedro Alves <palves@redhat.com>
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: gdb@sourceware.org
Subject: Re: Debugging 64-bit programs using 32-bit GDB
Date: Wed, 24 Jul 2013 14:33:00 -0000 [thread overview]
Message-ID: <51EFE5C0.60706@redhat.com> (raw)
In-Reply-To: <87r4f8oxo3.fsf@karetnikov.org>
On 07/09/2013 11:06 AM, Nikita Karetnikov wrote:
> Is it possible to debug a 64-bit executable ('bin/guile' [1]) using
> 32-bit GDB? (I use GNU/Linux.)
I don't think so. The ptrace registers interfaces allow retrieving
the right register sets (at least the modern interfaces), but
things like breakpoints, etc. won't work, as the 32-bit GDB won't
be able to handle the inferior's 64-bit addresses (due to how ptrace
works). Last I checked, Power had extra ptrace interfaces for that.
Don't know about MIPS.
(you can however connect a 32-bit GDB to a 64-bit GDBserver, and use
that to debug a 64-bit program, though that's more trouble
than just using a 64-bit GDB.).
>
> I've tried to configure GDB 7.6 with '--enable-64-bit-bfd' (see [2]),
> but it still shows "mips-tdep.c:709: internal-error: bad register
> size".
The x86_64 port catches the case early and bails out (amd64_linux_read_description):
if (sizeof (void *) == 4 && is_64bit && !is_x32)
error (_("Can't debug 64-bit process with 32-bit GDB"));
It'd be obviously better if MIPS native target did the same, instead
of tripping on assertions.
> [1] http://www.fdn.fr/~lcourtes/tmp/guile-static-stripped-2.0.9-mips64el-linux-gnuabi64.tar.xz
> [2] http://www.linux-mips.org/archives/linux-mips/2010-10/msg00336.html
--
Pedro Alves
next prev parent reply other threads:[~2013-07-24 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 10:02 Nikita Karetnikov
2013-07-24 14:33 ` Pedro Alves [this message]
2013-07-24 16:09 ` Doug Evans
2013-07-24 16:25 ` Pedro Alves
2013-07-24 17:14 ` Pedro Alves
2013-07-24 21:21 ` Maciej W. Rozycki
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=51EFE5C0.60706@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=nikita@karetnikov.org \
/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