This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdbserver 7.1 unable to read registers
- From: Jon Smirl <jonsmirl at gmail dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: William Wagner <will_wagner at carallon dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Fri, 24 Sep 2010 09:30:17 -0400
- Subject: Re: gdbserver 7.1 unable to read registers
- References: <4C9B8B8A.7030506@carallon.com> <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