From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3329 invoked by alias); 23 Aug 2003 23:03:30 -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 3280 invoked from network); 23 Aug 2003 23:03:18 -0000 Received: from unknown (HELO walton.kettenis.dyndns.org) (213.93.115.144) by sources.redhat.com with SMTP; 23 Aug 2003 23:03:18 -0000 Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2]) by walton.kettenis.dyndns.org (8.12.6p2/8.12.5) with ESMTP id h7NN3F0j006511; Sun, 24 Aug 2003 01:03:15 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6) with ESMTP id h7NN3FSN090236; Sun, 24 Aug 2003 01:03:15 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6/Submit) id h7NN3Ewp090233; Sun, 24 Aug 2003 01:03:14 +0200 (CEST) To: jiri@gaisler.com Cc: gdb@sources.redhat.com Subject: Re: The SPARC target References: <3F4111A9.4060600@gaisler.com> From: Mark Kettenis Date: Sat, 23 Aug 2003 23:03:00 -0000 In-Reply-To: Jiri Gaisler's message of "Mon, 18 Aug 2003 19:49:29 +0200" Message-ID: <868ypkt1sd.fsf@elgar.kettenis.dyndns.org> X-SW-Source: 2003-08/txt/msg00274.txt.bz2 Jiri Gaisler writes: > Mark Kettenis wrote: > > > Folks, > > > > The SPARC target has been unmaintained for quite some time now[1] > > (since november 2001) and it shows. It doesn't compile on FreeBSD, > > and running the testsuite on FreeBSD/sparc64 (after fixing it), > > Solaris 2.8 and NetBSD/sparc results in hundreds of unexpected > > failures with quite a few unresolved testcases. I think the target is > > bordering on (un)usability. > > > I would like to point out that the sparc port works quite well > for embedded (o/s unaware) 32-bit targets, at least up to gdb-5.3 . > There are some (minor) quirks with stack unwinding to form the > function backtrace, but overall it makes a good job. If you make > a new (64-bit) backend, could the old 32-bit backend remain, at > least the O/S independent parts? Well, most of the bitrot seems to have taken place after the 5.3 release. So I'm not at all confident that it still works to your satisfaction. I'm working on the 32-bit SPARC target now, and I'm pretty confident that I can get it in a shape where it works better than GDB 5.3. It's not until then that I'll replace the old code with my new implementation. Just out of curiosity. What's the --target you use to configure the GDB you're using to debug your embedded system? Mark