From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24759 invoked by alias); 15 Nov 2005 01:07:27 -0000 Received: (qmail 24387 invoked by uid 22791); 15 Nov 2005 01:07:23 -0000 Received: from 69.0.103.46.adsl.snet.net (HELO Power-Mac-G5.local) (69.0.103.46) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 15 Nov 2005 01:07:23 +0000 Received: by Power-Mac-G5.local (Postfix, from userid 501) id 0DD02CB833; Mon, 14 Nov 2005 20:07:17 -0500 (EST) Date: Tue, 15 Nov 2005 01:07:00 -0000 From: Ron McCall To: gdb@sources.redhat.com Subject: Re: warning: (Internal error: pc 0xd00 in read in psymtab, but not in symtab.) Message-ID: <20051115010716.GA14640@Power-Mac-G5.local> Mail-Followup-To: gdb@sources.redhat.com References: <20051108150752.62145.qmail@web81211.mail.mud.yahoo.com> <20051113173904.GF1945@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051113173904.GF1945@nevyn.them.org> User-Agent: Mutt/1.4.2.1i 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/msg00277.txt.bz2 On Sun, Nov 13, 2005 at 12:39:04PM -0500, Daniel Jacobowitz wrote: > What debugging format are you using - stabs or dwarf2? I don't know > offhand what could be causing this, and it's unlikely that a newer > snapshot will make a difference - that's pretty current. I think it is dwarf2 (there are no sections with "stab" in the name, just using -g). I am using gcc-4.0.2 (also happens with gcc-4.0.1) with binutils 2.16.1 and newlib 1.13.0, all the latest (released) versions, in case that matters at all. By the way, I did try a newer snapshot but still got the same result, as you suspected. I ran the cross gdb under a native gdb to try to see what was happening. With a breakpoint on find_pc_sect_symtab() in symtab.c and a single command input of "disas 0xd00 0xd04" there are several calls to this function. I can re-run the test to get specific input values if that would help. If I remember correctly, the call that resulted in the warning message being printed had inputs of pc=0 and section=0. If I enter "disas main" instead, no warnings are printed. There is a symbol at 0xd00 named trace_exc and "disas trace_exc" also generates the warnings. Note that the trace exception handler is written in assembly (GNU as) and normally resides in a custom section named "excvectbl". However, I changed that to ".text" just to make sure it wasn't the custom section that was causing grief and that didn't help. Anything else I should look at? Thanks! Ron McCall