From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17739 invoked by alias); 30 Aug 2006 23:08:54 -0000 Received: (qmail 17728 invoked by uid 22791); 30 Aug 2006 23:08:53 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.palmsource.com (HELO mx2.palmsource.com) (12.7.175.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 30 Aug 2006 23:08:52 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id 95BB525E35; Wed, 30 Aug 2006 16:08:50 -0700 (PDT) Received: from mx2.palmsource.com ([127.0.0.1]) by localhost (mx2.palmsource.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05437-01-25; Wed, 30 Aug 2006 16:08:49 -0700 (PDT) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id 9311425E41; Wed, 30 Aug 2006 16:08:49 -0700 (PDT) Received: from 192.168.92.59 ([192.168.92.59]) by ussunex01.palmsource.com ([192.168.101.9]) via Exchange Front-End Server owa.palmsource.com ([10.0.20.17]) with Microsoft Exchange Server HTTP-DAV ; Wed, 30 Aug 2006 23:08:48 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 30 Aug 2006 16:08:48 -0700 Subject: Re: Error running remote gdb From: Michael Snyder To: "Bizhan Gholikhamseh (bgholikh)" Cc: gdb@sourceware.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 30 Aug 2006 23:08:00 -0000 Message-Id: <1156979328.31253.4.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00263.txt.bz2 On Wed, 2006-08-30 at 14:54 -0700, Bizhan Gholikhamseh (bgholikh) wrote: > Hi > On our custome based powerpc we are running Linux 2.6.11. > I am trying to run a sample debug session with gdbserver. > > On target board I typed: > gdbserver :portno > > Then on host system I typed: > gdb > gdb> target extended-remote :portno > gdb> b main > gdb> cont > > Then I got the following error on my host; > Ignoring packet erro, continuing... > Ignoring packet erro, continuing... > Reply contains invalid hex digit 116 Most likely, your gdbserver and your gdb have not agreed on a particular PPC architecture and register set. So gdbserver will send a message to gdb containing the register values, but gdb will think that the message is the wrong size. You can narrow this down by telling gdb: set debug remote on before issuing the "target remote" command. If this is the problem, it will be resolved by determining the best-match PPC architecture and setting gdb to expect that architecture before connecting, by using the "set architecture" command. Michael