From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22544 invoked by alias); 12 Jul 2002 16:02:48 -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 22520 invoked from network); 12 Jul 2002 16:02:46 -0000 Received: from unknown (HELO monopoly.uk.clara.net) (212.126.144.50) by sources.redhat.com with SMTP; 12 Jul 2002 16:02:46 -0000 Received: from adsl-solo-39-123.claranet.co.uk ([213.253.39.123] helo=picochip.com) by monopoly.uk.clara.net with esmtp (Exim 3.36 #8) id 17T2sX-00013O-00 for gdb@sources.redhat.com; Fri, 12 Jul 2002 17:02:45 +0100 Message-ID: <3D2EFDE0.159BCF83@picochip.com> Date: Fri, 12 Jul 2002 09:02:00 -0000 From: Dan Towner Organization: picoChip Designs Ltd. X-Accept-Language: en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: New object file parser? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-07/txt/msg00131.txt.bz2 Hi all, I am porting gdb to a new processor architecture (embedded multi-processor DSP). Currently, although we use gcc as our compiler, we have a proprietary assembler and linker, which generate non-standard object and executable files. Now, faced with the task of getting the symbol table information from the object file through to gdb, is it easier to: 1) Write a new parser for BFD. or 2) Write a converter which generates a standard object file format from our proprietary format. Whichever route I take, which object file would be the easier to deal with? From what I have seen, I think that a.out would be the best, but is there anything simpler? Dan, ============================================================================= Daniel Towner picoChip Designs Ltd., Riverside Buildings, 108, Walcot Street, BATH, BA1 5BG dant@picochip.com 07786 702589