From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13707 invoked by alias); 13 Apr 2007 15:09:41 -0000 Received: (qmail 13692 invoked by uid 22791); 13 Apr 2007 15:09:40 -0000 X-Spam-Check-By: sourceware.org Received: from return.false.org (HELO return.false.org) (66.207.162.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 13 Apr 2007 16:09:32 +0100 Received: from return.false.org (localhost [127.0.0.1]) by return.false.org (Postfix) with ESMTP id 430564B267; Fri, 13 Apr 2007 10:09:31 -0500 (CDT) Received: from caradoc.them.org (dsl093-172-095.pit1.dsl.speakeasy.net [66.93.172.95]) by return.false.org (Postfix) with ESMTP id 228C34B262; Fri, 13 Apr 2007 10:09:31 -0500 (CDT) Received: from drow by caradoc.them.org with local (Exim 4.63) (envelope-from ) id 1HcNP0-0005Ql-1c; Fri, 13 Apr 2007 11:09:30 -0400 Date: Fri, 13 Apr 2007 15:09:00 -0000 From: Daniel Jacobowitz To: Alex Gonzalez Cc: gdb@sourceware.org Subject: Re: Invalid hex digit 59 - Linux MIPS kernel debugging Message-ID: <20070413150929.GA20853@caradoc.them.org> Mail-Followup-To: Alex Gonzalez , gdb@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-04/txt/msg00091.txt.bz2 On Fri, Apr 13, 2007 at 04:01:35PM +0100, Alex Gonzalez wrote: > Hi, > > I am trying to debug the Linux MIPS kernel using gdb. > > I have the gdb stub in the kernel and gdb communicating through the > serial interface, I seem to be able to set a breakpoint but gdb never > hits it. It complains with a 'Reply contains invalid hex digit 59', > which I guess refers to the semicolon character used in the response. > > I enclose the session output in case someone can give me some pointers. Try a CVS snapshot of GDB. What's probably going on is that your GDB expects 64-bit registers, so it is confused to find a semicolon in the middle of a register value. -- Daniel Jacobowitz CodeSourcery