From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Random gdbserver question (x86)
Date: Wed, 31 Mar 2010 17:35:00 -0000 [thread overview]
Message-ID: <4BB387E1.3070702@vmware.com> (raw)
In-Reply-To: <201003310219.49529.pedro@codesourcery.com>
Pedro Alves wrote:
> On Wednesday 31 March 2010 00:40:34, Michael Snyder wrote:
>> Question -- is gdbserver "multi-arch" to the extent that a 32-bit
>> gdbserver (built with target = i386) can debug a 64-bit app?
>
> No, only the other way around. It's "multi-arch" to the extent
> that a linux 64-bit gdbserver (built with target = x86-64) can
> debug a 32-bit app. It used to only be, only 64x64 or 32x32 was
> possible; with multi-arch, 64x32 was made possible.
>
>> I ask because linux-x86-low.c is full of ifdefs on the architecture.
>> It looks like most of the 64-bit code won't be compiled if the
>> build machine is 32-bit.
>
> Correct.
And is that more-or-less true of gdb as well? I.e., if host/target
is x86_64-linux, then gdb can debug both 32 and 64 bit apps, but if
host/target is i386-linux, then gdb can only debug 32 bit apps?
Actually, I phrase it as a question even though I am pretty sure it
is true. My real question is "Why?". It seems to me that if we just
included amd64-linux-nat.o and amd64-*-tdep.o in the build, then
32-bit gdb should be able to debug 64-bit native apps.
next prev parent reply other threads:[~2010-03-31 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 23:40 Michael Snyder
2010-03-31 1:19 ` Pedro Alves
2010-03-31 17:27 ` Michael Snyder
2010-03-31 17:35 ` Michael Snyder [this message]
2010-03-31 17:43 ` Pedro Alves
2010-03-31 17:46 ` Michael Snyder
2010-03-31 17:48 ` Daniel Jacobowitz
2010-03-31 17:56 ` Michael Snyder
2010-03-31 17:57 ` Mark Kettenis
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=4BB387E1.3070702@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=pedro@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