Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Mitchell Fang" <mitchell.fang@gmail.com>
To: gdb@sourceware.org
Subject: Re: GDB stub - connection from 32 bit GDB or 64 bit GDB
Date: Wed, 27 Sep 2006 18:17:00 -0000	[thread overview]
Message-ID: <cbd6ac8b0609271117scb41b8dsfa58165f88fc33fa@mail.gmail.com> (raw)
In-Reply-To: <20060927175135.GA4736@nevyn.them.org>

On 9/27/06, Daniel Jacobowitz <drow@false.org> wrote:
> It always amazes me how a problem will be known but quiet for a couple
> of years, and then half a dozen people will look at it at once :-)
>
> On Wed, Sep 27, 2006 at 10:34:45AM -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.
>
> It's not possible.
>
> >  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.
>
> The stub shouldn't adapt: the GDB client should.  This may be of
> interest:
>   http://sourceware.org/ml/gdb-patches/2006-09/msg00187.html
>   http://sourceware.org/ml/gdb-patches/2006-09/msg00188.html
>
> I'm less optimistic I'll have my code out this week, but I'm still
> trying.  What architecture are you using?

The target architecture is PowerPC and the host architecture is i686 cygwin.

Thanks for your help and I will await your patch.

Mitchell

>
> --
> Daniel Jacobowitz
> CodeSourcery
>


  reply	other threads:[~2006-09-27 18:17 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 [this message]
2006-09-27 18:22     ` Jan Kratochvil
2006-09-27 18:27 ` Michael Snyder
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=cbd6ac8b0609271117scb41b8dsfa58165f88fc33fa@mail.gmail.com \
    --to=mitchell.fang@gmail.com \
    --cc=gdb@sourceware.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