From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23181 invoked by alias); 15 Nov 2005 23:25:28 -0000 Received: (qmail 23158 invoked by uid 22791); 15 Nov 2005 23:25:24 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 15 Nov 2005 23:25:24 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EcAAw-0006Rk-Gq; Tue, 15 Nov 2005 18:25:18 -0500 Date: Tue, 15 Nov 2005 23:25:00 -0000 From: Daniel Jacobowitz To: Jim Blandy Cc: Ron McCall , gdb@sources.redhat.com Subject: Re: warning: (Internal error: pc 0xd00 in read in psymtab, but not in symtab.) Message-ID: <20051115232518.GA24754@nevyn.them.org> Mail-Followup-To: Jim Blandy , Ron McCall , gdb@sources.redhat.com References: <20051115204629.32845.qmail@web81206.mail.mud.yahoo.com> <8f2776cb0511151510p1d7fe81dl7aa7a6b439b4622@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8f2776cb0511151510p1d7fe81dl7aa7a6b439b4622@mail.gmail.com> User-Agent: Mutt/1.5.8i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00301.txt.bz2 On Tue, Nov 15, 2005 at 03:10:52PM -0800, Jim Blandy wrote: > Fixing this entails some more reliable method of recognizing debug > info referring to functions or variables in deleted sections than what > we have now. Perhaps one of our linker fanatics knows of the Right > Way? We would need to verify that the section was Actually Present In The Binary somehow. Maybe by its symbols, maybe not. > One possibility might be to tighten up the heuristic. Presumably, if > a function's low address is at zero because the function is really > located at the bottom of the address space, then its high address > won't be zero. But if the function was deleted, both the high and low > PC will be zero. No, that doesn't work. The high address is probably .gnu.linkonce.foo+0x104, which may show up as 0x104 depending on the relocation format in use. -- Daniel Jacobowitz CodeSourcery, LLC