From: William Wagner <will_wagner@carallon.com>
To: "'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: gdbserver 7.1 unable to read registers
Date: Thu, 23 Sep 2010 17:17:00 -0000 [thread overview]
Message-ID: <4C9B8B8A.7030506@carallon.com> (raw)
Hello All,
I have built up a cross toolchain for an arm target with an x64 host. I
have compiled gdb/gdbserver 7.1.
When I try to debug my application I can connect to gdbserver fine but I
get an error when gdb tries to read the registers:
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, however I
compiled gdb and gdbserver with the same options.
How can I tell what register information gdb is expecting? Is there some
either a compile time or runtime option I need to set with gdb so they
agree on numbers of registers?
Thanks
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner@carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next reply other threads:[~2010-09-23 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 17:17 William Wagner [this message]
2010-09-24 7:47 ` Jan Kratochvil
2010-09-24 7:54 ` William Wagner
2010-09-24 13:30 ` Jon Smirl
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=4C9B8B8A.7030506@carallon.com \
--to=will_wagner@carallon.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