From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8829 invoked by alias); 12 Dec 2006 16:39:30 -0000 Received: (qmail 8819 invoked by uid 22791); 12 Dec 2006 16:39:29 -0000 X-Spam-Check-By: sourceware.org Received: from mxout.hispeed.ch (HELO smtp.hispeed.ch) (62.2.95.247) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 12 Dec 2006 16:39:22 +0000 Received: from indel.ch (84-73-11-232.dclient.hispeed.ch [84.73.11.232]) by smtp.hispeed.ch (8.12.11.20060308/8.12.11/taifun-1.0) with SMTP id kBCGdI3x032084 for ; Tue, 12 Dec 2006 17:39:19 +0100 Received: from FABI.indel.ch [192.168.1.91] by indel.ch [127.0.0.1] with SMTP (MDaemon.v2.7.SP5.R) for ; Tue, 12 Dec 2006 17:39:13 +0100 Message-Id: <5.2.0.9.1.20061212102328.0187a8c0@NT_SERVER> X-Sender: cenedese@NT_SERVER (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 12 Dec 2006 16:39:00 -0000 To: gdb@sourceware.org From: Fabian Cenedese Subject: Re: Wrong source location in symbols In-Reply-To: <20061211165025.GA4815@nevyn.them.org> References: <5.2.0.9.1.20061211174350.01b23e70@NT_SERVER> <5.2.0.9.1.20061211104829.0186dcc0@NT_SERVER> <5.2.0.9.1.20061211104829.0186dcc0@NT_SERVER> <5.2.0.9.1.20061211174350.01b23e70@NT_SERVER> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MDaemon-Deliver-To: gdb@sourceware.org X-Return-Path: cenedese@indel.ch X-Virus-Status: Clean X-DCC-spamcheck-02.tornado.cablecom.ch-Metrics: smtp-06.tornado.cablecom.ch 1378; Body=1 Fuz1=1 Fuz2=1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-12/txt/msg00102.txt.bz2 At 11:50 11.12.2006 -0500, Daniel Jacobowitz wrote: >On Mon, Dec 11, 2006 at 05:48:24PM +0100, Fabian Cenedese wrote: >> I couldn't quite make out in symtab.c a place where the filenames >> get set. But I saw in elfread.c, elf_symtab_read that quite some >> minsyms got the filename write.c set though they are not in this >> source file. I'll see what else I can find. > >It's not set per se; it's looked up when needed. Start with the code >that prints out the dump and work from there. It's exactly the minsymbol filename which is set in above mentioned function and always enclosed with SOFUN_ADDRESS_MAYBE_MISSING. I found that many symbols get as filename the most recently used filename (not only write.c) even if it's wrong. It seems like there are some file symbols missing/not read or in wrong order or whatever. Apart from one comparison this filename is only used for displaying, so I guess I shouldn't rely on its content too much. But still... I leave that for the moment and write in another post about other problems. Thanks bye Fabi