From: Jon Smirl <jonsmirl@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: William Wagner <will_wagner@carallon.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: gdbserver 7.1 unable to read registers
Date: Fri, 24 Sep 2010 13:30:00 -0000 [thread overview]
Message-ID: <AANLkTikwAPgfOUb_z3pg5trxYyTOVLU5QDmj2pUBG4F+@mail.gmail.com> (raw)
In-Reply-To: <20100924074709.GA6017@host1.dyn.jankratochvil.net>
On Fri, Sep 24, 2010 at 3:47 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Thu, 23 Sep 2010 19:16:58 +0200, William Wagner wrote:
>> Remote 'g' packet reply is too long: 00000000b07edbbe0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c07ddbbe00000000a007004010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
>>
>> As far as I can tell the error is because the target and the host
>> disagree as to how many registers there are on the target,
>
> While I have seen it only on i386<->x86_64 it should be the same problem:
> http://sourceware.org/gdb/wiki/FAQ#line-53
> 15. When connecting to gdbserver I get Remote register badly formatted, g packet
> reply to long etc.
> Your gdb 32bit/64bit architecture setting may not match that of gdbserver. Try
> to load the executable by file first. You may also check set/show architecture.
I couldn't figure out a solution to this error for months until I
stumbled onto this conversation:
http://old.nabble.com/Switching-architectures-from-a-remote-target-td27458511.html
I gave up on 64b qemu kernel debugging and went back to 32b.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2010-09-24 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 17:17 William Wagner
2010-09-24 7:47 ` Jan Kratochvil
2010-09-24 7:54 ` William Wagner
2010-09-24 13:30 ` Jon Smirl [this message]
2010-09-24 12:58 ` Ulrich Weigand
2010-09-24 13:36 ` Pedro Alves
2010-09-24 13:44 ` William Wagner
2010-09-24 14:05 ` Ulrich Weigand
2010-09-24 14:39 ` Pedro Alves
2010-09-27 10:25 ` Steffen Dettmer
2010-09-27 14:44 ` Daniel Jacobowitz
2010-10-07 17:16 ` Ulrich Weigand
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=AANLkTikwAPgfOUb_z3pg5trxYyTOVLU5QDmj2pUBG4F+@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=will_wagner@carallon.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