From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3827 invoked by alias); 14 Aug 2003 23:28:12 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 3816 invoked from network); 14 Aug 2003 23:28:11 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 14 Aug 2003 23:28:11 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h7ENSBt18944 for ; Thu, 14 Aug 2003 19:28:11 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h7ENSBs09786; Thu, 14 Aug 2003 19:28:11 -0400 Received: from [150.1.200.14] (vpn50-56.rdu.redhat.com [172.16.50.56]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id h7ENS9ED009821; Thu, 14 Aug 2003 19:28:10 -0400 Subject: Re: duplicated source file names From: Keith Seitz To: jwilliams@itee.uq.edu.au Cc: "insight@sources.redhat.com" In-Reply-To: <3F3C06C7.5090006@itee.uq.edu.au> References: <3F3B355C.5040904@itee.uq.edu.au> <1060877014.1578.17.camel@lindt.uglyboxes.com> <3F3C06C7.5090006@itee.uq.edu.au> Content-Type: text/plain Organization: Message-Id: <1060903735.1578.33.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Date: Thu, 14 Aug 2003 23:28:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q3/txt/msg00100.txt.bz2 On Thu, 2003-08-14 at 15:01, John Williams wrote: > > - "list ext2_read_super": Does it return the correct source? > > Nope - it lists the "correct" line numbers from the wrong file. I'm > guessing this is a problem in the binutils addr2line, is that what it's for? Close. Binutils doesn't really read debug info the way gdb does. They both try to do the same thing, but gdb looks at it slightly differently. > > - "tk gdbtk_loc ext_read_super": Right info? > > I get - Error: invalid command name "gdbtk_loc" Oops. Should have been "gdb_loc" not "gdbtk_loc". > Yeah I realise that - this is a cross-debugger for an embedded system, > short of forward-porting it myself (*not* gonna happen!) I don't really > have a lot of options. Ah. Understood. > I'm not too stressed about this, I can just rename the source file and > rebuild the project as I need to, just wanted to know if there was > something simple I might do. > Yeah -- that's been the sad approach used by most. As I recall we have a file in gdb that used to use the same filename as another file in bfd. Instead fixing gdb, someone renamed gdb's file! Keith