From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12760 invoked by alias); 13 Nov 2002 10:23:24 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 12752 invoked from network); 13 Nov 2002 10:23:22 -0000 Received: from unknown (HELO dell.zee2.com) (212.74.13.151) by sources.redhat.com with SMTP; 13 Nov 2002 10:23:22 -0000 Received: from zee2.com (localhost [127.0.0.1]) by dell.zee2.com (8.11.6/8.11.6) with ESMTP id gADANDn11377; Wed, 13 Nov 2002 05:23:14 -0500 Message-ID: <3DD22811.3AB603DC@zee2.com> Date: Wed, 13 Nov 2002 02:23:00 -0000 From: Stuart Hughes Organization: Zee2 Ltd X-Accept-Language: en MIME-Version: 1.0 To: Daniel Jacobowitz CC: Robert Schwebel , gdb@sources.redhat.com Subject: Re: Cross gdb for ARM References: <20021112180818.GT29603@pengutronix.de> <20021112181332.GA17863@nevyn.them.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-11/txt/msg00136.txt.bz2 Daniel Jacobowitz wrote: > > On Tue, Nov 12, 2002 at 07:08:18PM +0100, Robert Schwebel wrote: > > Hi, > > > > which version of gdb/gdbserver is currently recommended for StrongARM? > > I've tried 5.2 and 5.2.1, but both do not work. I can start the program > > on the target remotely with "run", but I cannot set breakpoints. It > > simply continues running and doesn't stop. > > 5.2 should work. More details? > > > I also wanted to try CVS, but it doesn't compile at the moment: > > Get a 5.3 or trunk snapshot from the > sources.redhat.com/pub/gdb/snapshots directory; that won't include SID. Hi Robert, FWIW, I've been doing something similar, with gdb/gdbserver 5.2 and with the 5.3 CVS branch (the main difference is that the 5.3 has thread support, which Daniel did. I tried this on mips and it works great, but I've not tried it on arm yet). As far as the not stopping goes, this may be the same problem that I reported a week ago (look for software single step in the archives). With Daniel's assistance, I've been able to isolate the problem (same on 5.2 and 5.3), and I have a fix. Once I've cleaned up and checked it, I'll send an patch and an explanation to the list (replying to software single step thread), hopefully I should get that done today. Regards, Stuart