From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2093 invoked by alias); 13 Apr 2007 17:29:28 -0000 Received: (qmail 2076 invoked by uid 22791); 13 Apr 2007 17:29:27 -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 18:29:25 +0100 Received: from return.false.org (localhost [127.0.0.1]) by return.false.org (Postfix) with ESMTP id A757C4B267; Fri, 13 Apr 2007 12:29:24 -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 92ED84B262; Fri, 13 Apr 2007 12:29:24 -0500 (CDT) Received: from drow by caradoc.them.org with local (Exim 4.63) (envelope-from ) id 1HcPaN-00071m-Vd; Fri, 13 Apr 2007 13:29:23 -0400 Date: Fri, 13 Apr 2007 17:29:00 -0000 From: Daniel Jacobowitz To: Alex Gonzalez Cc: gdb@sourceware.org Subject: Re: Invalid hex digit 59 - Linux MIPS kernel debugging Message-ID: <20070413172923.GA26847@caradoc.them.org> Mail-Followup-To: Alex Gonzalez , gdb@sourceware.org References: <20070413150929.GA20853@caradoc.them.org> 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/msg00094.txt.bz2 On Fri, Apr 13, 2007 at 05:40:25PM +0100, Alex Gonzalez wrote: > Thanks, I'll try that. > > If you don't mind me asking, why would gdb expect 64bits registers > when the target abi is set to o32? Because you can run o32 binaries on hardware with 64-bit registers, and there are some ugly corner cases where the upper half of registers can cause problems - e.g. for things which have undefined behavior if the input registers are not correctly sign extended. You've probably built a 32-bit kernel for a processor that GDB knows is actually 64-bit. But if your debug agent only supplies 32 bits, then GDB will get along fine (once it knows that). If you don't want to change GDB versions, an appropriate "set arch" might work - but I recommend the current snapshots. -- Daniel Jacobowitz CodeSourcery