From: Michael Snyder <msnyder@specifix.com>
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: Thu, 14 Aug 2008 15:03:00 -0000 [thread overview]
Message-ID: <1218589302.3549.710.camel@localhost.localdomain> (raw)
In-Reply-To: <48A0F96E.7000701@oarcorp.com>
On Mon, 2008-08-11 at 21:46 -0500, Joel Sherrill wrote:
> Hi,
>
> 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
>
> Michael tried gdb 6.8 targeting m68k-linux and
> it connects OK.
>
> I tried gdb 6.6 m68k-rtems and it connects and
> appears to work OK.
>
> It looks like the way the maximum packet size is
> calculated has changed since 6.6 and is dependent
> on number of registers.
>
> Does anyone see what the subtle difference is that
> is breaking it for m68k-rtems?
I have run into something similar -- yes there was a change in the way
this was computed, in fact I don't think it used to ever check if the
packet was too long (only if it was too short).
prev parent reply other threads:[~2008-08-13 1:02 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
2008-08-14 15:03 ` Michael Snyder [this message]
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=1218589302.3549.710.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--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