From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24180 invoked by alias); 10 Sep 2003 07:56:00 -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 24145 invoked from network); 10 Sep 2003 07:55:58 -0000 Received: from unknown (HELO steve.softier.local) (62.90.245.250) by sources.redhat.com with SMTP; 10 Sep 2003 07:55:58 -0000 Received: from steve.softier.local (localhost.localdomain [127.0.0.1]) by steve.softier.local (8.12.8/8.12.8) with ESMTP id h8A7tuQs031076 for ; Wed, 10 Sep 2003 10:55:56 +0300 Received: (from steve@localhost) by steve.softier.local (8.12.8/8.12.8/Submit) id h8A7ttIO031074 for gdb@sources.redhat.com; Wed, 10 Sep 2003 10:55:55 +0300 X-Authentication-Warning: steve.softier.local: steve set sender to xyzzy@hotpop.com using -f Subject: Re: TI C6x support From: Stephen Biggs To: GDB list In-Reply-To: <1062318060.15365.10.camel@steve.softier.local> References: <1062318060.15365.10.camel@steve.softier.local> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1063180555.31842.0.camel@steve.softier.local> Mime-Version: 1.0 Date: Wed, 10 Sep 2003 07:56:00 -0000 X-SW-Source: 2003-09/txt/msg00134.txt.bz2 May I ask why nobody has answered me? On Sun, 2003-08-31 at 11:21, Stephen Biggs wrote: > I am adding full support for the TI C6X (mostly C64xx) chip to BFD and > GDB. I intend to submit a patch as soon as stability of my port and > company politics allow. > > I am stuck. > > It seems that the COFF version of GDB creates a fake symbol table with a > filename of "_globals_" and language. This is not working for > me. I compile with Dwarf2 and have all the symbols and the symbols show > up in a dump as correct for the C file. When I try to "disassemble > main", I get back the response "main is not a function". This is the > same response I get when I try "list". Disassembly using the raw > address of "main" works just fine. > > I am trying to decipher the code that causes these messages but am > running into a wall. I know that this is something stupid on my part > and quite simple, but I just can't get it. > > Any help would be appreciated. >