From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13610 invoked by alias); 6 Nov 2003 00:29:08 -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 13601 invoked from network); 6 Nov 2003 00:29:07 -0000 Received: from unknown (HELO gum.itee.uq.edu.au) (130.102.66.1) by sources.redhat.com with SMTP; 6 Nov 2003 00:29:07 -0000 Received: from nut.itee.uq.edu.au (nut.itee.uq.edu.au [130.102.66.13]) by gum.itee.uq.edu.au (8.12.10/8.12.9) with ESMTP id hA60SsqR028634 for ; Thu, 6 Nov 2003 10:28:54 +1000 (EST) Received: from itee.uq.edu.au (g435-9029.itee.uq.edu.au [130.102.66.250]) by nut.itee.uq.edu.au (8.12.10/8.12.9) with ESMTP id hA60SrSq005856 for ; Thu, 6 Nov 2003 10:28:53 +1000 (EST) Message-ID: <3FA99AB8.60908@itee.uq.edu.au> Date: Thu, 06 Nov 2003 00:29:00 -0000 From: John Williams Reply-To: jwilliams@itee.uq.edu.au Organization: ITEE, University of Queensland User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: gdbserver version quandry Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checked: This message probably not SPAM X-Spam-Score: -0.1 X-Spam-Tests: USER_AGENT_MOZILLA_UA,X_ACCEPT_LANG X-Spam-Report: -0.10 points, 8 required; * 0.0 -- User-Agent header indicates a non-spam MUA (Mozilla) * -0.1 -- Has a X-Accept-Language header X-Scanned-By: MIMEDefang 2.35 X-SW-Source: 2003-11/txt/msg00046.txt.bz2 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. Thanks, John