From: Andreas Schwab <schwab@suse.de>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: <gdb@sourceware.org>, kang shuo <blackfin.kang@gmail.com>
Subject: Re: m68k gdb issue with skyeye
Date: Wed, 13 Aug 2008 00:18:00 -0000 [thread overview]
Message-ID: <jetzdq5i32.fsf@sykes.suse.de> (raw)
In-Reply-To: <48A0F96E.7000701@oarcorp.com> (Joel Sherrill's message of "Mon, 11 Aug 2008 21:46:06 -0500")
Joel Sherrill <joel.sherrill@oarcorp.com> writes:
> Michael Kang and I have run into something with
> m68k gdb and don't know how to fix it. The executable
> is for a coldfire mc5272.
>
> With m68k-rtems* (basically m68k-elf) on gdb 6.8,
> connecting to the Skyeye gdbserver gives this.
>
> (gdb) tar remote :12345
> Remote debugging using :12345
> Remote 'g' packet reply is too long:
> 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
That probably means the server and the debugger don't agree about the
size of the floating point registers. The coldfire has only 64-bit fp
regs.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-08-12 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 19:23 Joel Sherrill
2008-08-13 0:18 ` Andreas Schwab [this message]
2008-08-14 15:03 ` Michael Snyder
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=jetzdq5i32.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=blackfin.kang@gmail.com \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@oarcorp.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