From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27051 invoked by alias); 26 Nov 2002 15:01:01 -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 27031 invoked from network); 26 Nov 2002 15:00:59 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 26 Nov 2002 15:00:59 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 9E5D53F30; Tue, 26 Nov 2002 10:00:53 -0500 (EST) Message-ID: <3DE38CA5.3080302@redhat.com> Date: Tue, 26 Nov 2002 07:01:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: James Sampson Cc: GDB Archive Subject: Re: Porting GDB - Where to start? References: <20021126084143.87BD12D6E9@postfix2.ofir.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-11/txt/msg00368.txt.bz2 >>> It's an ELF port, but xstormy16 is still probably your best bet. > >> >>Yes. >> >>(GDB ports are object file netural. Handling elf, xcoff, coff, ... is a >>bfd problem and as long as BFD can handle it, so can GDB. The only >>potential got-ya is the debug info, use GCC and you should be safe >there.) > > > Ok then :-) > > A couple of questions: > > 1. Why is xstormy16 the best place to start?. Being fairly new, and for a relatively straightforward architecture, it doesn't come with much baggage. It's roughly 1000 lines long, while the MIPS is a wopping 6000 lines! > 2. Since I can't use GCC to make target specific code for a C55x I must use > CCS (Code Composer Studio) from TI. What could a "got-ya" be?. There is a good chance that after you've kind of got the target `mostly' working, you will spend time debugging problems in the symtab code. This is because, when it comes to debug info, no two compilers are alike. Consequently, is a very good chance that GDB won't properly handle the debug info being output by this compiler. Anyway, a first step is to find out what the debug info is and if GDB has any support for it at all .... One way is to compile a simple program using `-g -S' and then look at the assembler that is created. If it contains ``.stabn'' lines its stabs, if it contains ``.debug_...'' symbols it's dwarf2 (or dwarf1?). Beyond that, you may want to post the contents here. (btw, anyone got an easier way of identifying the debug info?) Andrew