Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Michael Snyder <msnyder@vmware.com>,
	  Pedro Alves <pedro@codesourcery.com>,
	 "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Random gdbserver question (x86)
Date: Wed, 31 Mar 2010 17:56:00 -0000	[thread overview]
Message-ID: <4BB38CAA.6070901@vmware.com> (raw)
In-Reply-To: <20100331174749.GA16865@caradoc.them.org>

Daniel Jacobowitz wrote:
> On Wed, Mar 31, 2010 at 10:35:29AM -0700, Michael Snyder wrote:
>> 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.
> 
> I don't think the necessary kernel interfaces exist.  Or at least, we
> aren't using them.  Compare the offsets in the two nat files.
> 

Hmmm, but both nat files get linked in when we do a 64 bit build.

Suppose I wanted to build gdb on a 32 bit host, but use it on a
64 bit host.  If I specify "target=x86_64-linux", then my gdb will
not work natively on *either* host, because it will be built as a
cross-only debugger.


  reply	other threads:[~2010-03-31 17:56 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
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 [this message]
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=4BB38CAA.6070901@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