From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17056 invoked by alias); 6 Nov 2003 00:39:45 -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 17030 invoked from network); 6 Nov 2003 00:39:42 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 6 Nov 2003 00:39:42 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1AHYBT-0003LJ-PX; Wed, 05 Nov 2003 19:39:35 -0500 Date: Thu, 06 Nov 2003 00:39:00 -0000 From: Daniel Jacobowitz To: John Williams Cc: gdb@sources.redhat.com Subject: Re: gdbserver version quandry Message-ID: <20031106003935.GA12798@nevyn.them.org> Mail-Followup-To: John Williams , gdb@sources.redhat.com References: <3FA99AB8.60908@itee.uq.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA99AB8.60908@itee.uq.edu.au> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-11/txt/msg00047.txt.bz2 On Thu, Nov 06, 2003 at 10:50:00AM +1000, John Williams wrote: > Hi folks, > > I have recently completed a port of uClinux to the Xilinx Microblaze > soft-processor architecture. > > http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux. > > I am now investigating providing gdbserver support for this architecture. > > Xilinx ported gcc 2.95 and gdb 5.0 (20010428-1) to support microblaze - > as I understand it they have no intention of moving forward to a newer > version of gdb. > > So, I think I'm stuck with porting gdbserver from gdb5.0, right? I know > this is ancient history, but I don't think I'm about to undertake the > job of adding a new arch to gdb 6.0... > > Some pertinent facts: > > 1- Miles Bader, who did the v850 port of uClinux and gdbserver, has a > nice clean script and patch to morph gdbserver 5.1 to support uClinux. > > 2 - The standard uClinux distribution supported by Snapgear, has a > hacked version of gdbserver 4.12.3 to support uClinux, but hard-coded > for m68k arch support only. > > So, the question is: Would it be cleaner for me to > > (a) Back-port gdbserver 5.1 to support the gdb 5.0 interface; > (b) Forward port and Clean up the m68k uClinux gdbserver 4.12.3 to > support the gdb5.0 and microblaze; or > (c) Start from scratch with gdbserver 5.0 and provide microblaze support > directly? > > I'm thinking (a) or (c), depending on how much changed in the > gdb<->gdbserver communication protocol between 5.0 and 5.1. Is there > any online documentation on this - in particular regarding how it > changed from 5.0 to 5.1? > > Superficially - Miles' scripts and patches don't apply cleanly to > gdbserver 5.0 - some file/directory structures have changed. > > Any advice or pointers would be greatly appreciated. I can't offer you any useful advice. I didn't start seriously cleaning up gdbserver until 5.2. If your gdb 5.0 port supports remote debugging at all, then probably easiest is to take the most recent version of gdbserver and work from that. Then adapt it to speak to your older client. Not much should be required. Anything else is a dead end. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer