From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-23004-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 15296 invoked by alias); 3 Nov 2005 21:19:50 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
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
Received: (qmail 15287 invoked by uid 22791); 3 Nov 2005 21:19:48 -0000
Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 03 Nov 2005 21:19:48 +0000
Received: from drow by nevyn.them.org with local (Exim 4.54)
	id 1EXmUN-000320-8S; Thu, 03 Nov 2005 16:19:15 -0500
Date: Thu, 03 Nov 2005 21:19:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: Efim Monjak <ymonyak@lipowsky.de>
Cc: gdb@sources.redhat.com
Subject: Re: remote failure reply
Message-ID: <20051103211915.GC11262@nevyn.them.org>
Mail-Followup-To: Efim Monjak <ymonyak@lipowsky.de>, gdb@sources.redhat.com
References: <436A5BA0.7090803@lipowsky.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <436A5BA0.7090803@lipowsky.de>
User-Agent: Mutt/1.5.8i
X-SW-Source: 2005-11/txt/msg00074.txt.bz2

On Thu, Nov 03, 2005 at 07:49:04PM +0100, Efim Monjak wrote:
> Hi all,
> 
> I try to debug a relatively big programm with arm-elf-gdb 6.3.50. After 
> a couple of steps I receive a failure message from GDB
> about register message. But later the GDB has receive an other register 
> message withother failure.
> Can you tell me what is hier a problem? As I used GDB 6.1 I have had a 
> problem with remote target
> depend on Walues in Registers. In this case GDB sent +---+--- .... In 
> snapshort 6.3.50 it is fixed.
> Possibly it is now a similar problem.

This is why it's traditional to use lowercase hex, not uppercase, in
remote replies.

> Packet received: 
> E03D004032000000D13C004002000000800000003CFEFF7F2C01004000000000DC813F28F26AC140F03B0040EC3D0040703C0040C83C0040F00F0080F40B0080000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005F000020

This is interpreted as an error because it begins with 'E'.

Perhaps it shouldn't be, but for compatibility, I recommend fixing the
stub.

-- 
Daniel Jacobowitz
CodeSourcery, LLC