From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 353 invoked by alias); 5 Jun 2009 12:21:04 -0000 Received: (qmail 345 invoked by uid 22791); 5 Jun 2009 12:21:03 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Jun 2009 12:20:54 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id DD41610F69; Fri, 5 Jun 2009 12:20:51 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id C47CC10E5D; Fri, 5 Jun 2009 12:20:51 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MCYPi-0004WU-Os; Fri, 05 Jun 2009 08:20:50 -0400 Date: Fri, 05 Jun 2009 12:21:00 -0000 From: Daniel Jacobowitz To: "Vellemans, Noel" Cc: gdb@sourceware.org Subject: Re: GDB/GDBSERVER 6.8 for ARM targets not working ?? Message-ID: <20090605122050.GA16926@caradoc.them.org> Mail-Followup-To: "Vellemans, Noel" , gdb@sourceware.org References: <1531E53627F1F749B4FE809BF2A4EB6701009203@WETMEX10.loepfe.com> <1531E53627F1F749B4FE809BF2A4EB6701009339@WETMEX10.loepfe.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1531E53627F1F749B4FE809BF2A4EB6701009339@WETMEX10.loepfe.com> User-Agent: Mutt/1.5.17 (2008-05-11) 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: 2009-06/txt/msg00049.txt.bz2 On Fri, Jun 05, 2009 at 01:03:05PM +0200, Vellemans, Noel wrote: > > Hi guy's > > > Took me some time ... But ... just got it working by falling back to > 6.7.1. > > > So GDB/GDBSERVER 6.8 must be broken for ARM. It definitely isn't. I used it for months, and similar cases to your example are in the testsuite. Most ARM/GDB users use GLIBC though. You're using uClibc; it could be a bug in uClibc triggered by interaction with the newer gdbserver. This can be tricky to build and set up; if you're having trouble, there are lots of places to get a preconfigured working copy, and even support. -- Daniel Jacobowitz CodeSourcery