Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Mitchell Fang <mitchell.fang@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB stub - connection from 32 bit GDB or 64 bit GDB
Date: Wed, 27 Sep 2006 18:27:00 -0000	[thread overview]
Message-ID: <1159381625.9768.51.camel@localhost.localdomain> (raw)
In-Reply-To: <cbd6ac8b0609271034r311962aakc04753114eec404c@mail.gmail.com>

On Wed, 2006-09-27 at 10:34 -0700, Mitchell Fang wrote:
> Hi,
> 
>   How can the gdb stub know if a 32 bit GDB is connecting to the stub
> or a 64 bit GDB is connecting to the stub?   Is it even possible?  It
> doesn't seem possible to me looking at the current gdb remote
> commands, but hopefully I overlooked something.
>   I have tried different combinations with 32-bit and 64-bit GDBs and
> gdbservers and it seems like a 32 bit GDB will not work with a 64 bit
> gdbserver and vice versa.

In general, a stub is built for a single architecture, while gdb
may be built to handle several architecture variants (such as 32 bit
and 64 bit versions of the same processor family).  Therefore in
practice, to my knowledge, it's never the stub that adapts to gdb, 
it's gdb that adapts to the stub.

That's not to say that it's prohibited, but there's currently
no provision for it in the remote protocol.

However, there *is* provision for a general purpose query
(get/set) request.  You could use that to, say, tell your 
(custom) stub which version of the architecture you wanted
to talk to.

See the "Q"/"q" messages.

Michael



  parent reply	other threads:[~2006-09-27 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 17:34 Mitchell Fang
2006-09-27 17:51 ` Daniel Jacobowitz
2006-09-27 18:17   ` Mitchell Fang
2006-09-27 18:22     ` Jan Kratochvil
2006-09-27 18:27 ` Michael Snyder [this message]
2006-09-27 19:58 ` Jim Blandy

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=1159381625.9768.51.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=gdb@sourceware.org \
    --cc=mitchell.fang@gmail.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