From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdbserver build broken on amd64-linux
Date: Thu, 21 Oct 2004 17:36:00 -0000 [thread overview]
Message-ID: <20041021173645.GA7716@nevyn.them.org> (raw)
In-Reply-To: <20041021173336.GW21300@gnat.com>
On Thu, Oct 21, 2004 at 10:33:36AM -0700, Joel Brobecker wrote:
> > > I tried it, I had a failure:
> > >
> > > (gdb) target remote localhost:2345
> > > Remote debugging using localhost:2345
> > > Couldn't establish connection to remote target
> > > Remote register badly formatted: T0506:0000000000000000;07:c0f1ffbf7f000000;10:2
> > > 06f55952a000000;
> > > here: 0000000;07:c0f1ffbf7f000000;10:206f55952a000000;
> > >
> > > Not sure why there seems to be discrepancy in the protocol...
> >
> > The host GDB is configured for amd64 rather than i386, right? And
> > you've loaded a 64-bit binary using "file"? That error means GDB
> > expected a 32-bit register.
>
> Both the host gdb and gdbserver come from the same build on the same
> machine. So you're right, GDB was configured for amd64. But I don't
> understand the reference to i386. Do you mean gdbserver on amd64 only
> supports i386 binaries?
Bad phrasing: I was just verifying that it was amd64 rather than i386,
as a possible source of error. You'll have to work out why your host
GDB expects only a 32-bit number.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-10-21 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 5:32 Joel Brobecker
2004-10-20 14:26 ` Daniel Jacobowitz
2004-10-20 15:24 ` Joel Brobecker
2004-10-20 15:47 ` Mark Kettenis
2004-10-20 15:53 ` Daniel Jacobowitz
2004-10-21 4:15 ` Joel Brobecker
2004-10-21 4:38 ` Joel Brobecker
2004-10-21 13:48 ` Daniel Jacobowitz
2004-10-21 17:27 ` Joel Brobecker
2004-10-21 13:49 ` Daniel Jacobowitz
2004-10-21 17:33 ` Joel Brobecker
2004-10-21 17:36 ` Daniel Jacobowitz [this message]
2004-10-21 18:09 ` Joel Brobecker
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=20041021173645.GA7716@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.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