From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-32820-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 14255 invoked by alias); 13 Aug 2008 01:02:32 -0000
Received: (qmail 14242 invoked by uid 22791); 13 Aug 2008 01:02:30 -0000
X-Spam-Check-By: sourceware.org
Received: from bluesmobile.specifix.com (HELO bluesmobile.specifix.com) (216.129.118.140)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 13 Aug 2008 01:01:43 +0000
Received: from [127.0.0.1] (bluesmobile.specifix.com [216.129.118.140]) 	by bluesmobile.specifix.com (Postfix) with ESMTP id 4FCF23BFF5; 	Tue, 12 Aug 2008 18:01:42 -0700 (PDT)
Subject: Re: m68k gdb issue with skyeye
From: Michael Snyder <msnyder@specifix.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: gdb@sourceware.org, kang shuo <blackfin.kang@gmail.com>
In-Reply-To: <48A0F96E.7000701@oarcorp.com>
References: <48A0F96E.7000701@oarcorp.com>
Content-Type: text/plain
Date: Thu, 14 Aug 2008 15:03:00 -0000
Message-Id: <1218589302.3549.710.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.3 (2.10.3-7.fc7)
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-08/txt/msg00173.txt.bz2

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).