From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28940 invoked by alias); 13 Sep 2002 22:01:02 -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 28919 invoked from network); 13 Sep 2002 22:01:01 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 13 Sep 2002 22:01:01 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17pzQk-0002n5-00; Fri, 13 Sep 2002 18:00:54 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17pyUw-0005nJ-00; Fri, 13 Sep 2002 18:01:10 -0400 Date: Fri, 13 Sep 2002 15:01:00 -0000 From: Daniel Jacobowitz To: Earl Chew Cc: gdb@sources.redhat.com Subject: Re: Mystified by "Internal error: pc 0x89f21e10 read in psymtab, but not in symtab Message-ID: <20020913220110.GA22097@nevyn.them.org> Mail-Followup-To: Earl Chew , gdb@sources.redhat.com References: <3D825BB5.48CFAFAB@agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D825BB5.48CFAFAB@agilent.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-09/txt/msg00166.txt.bz2 On Fri, Sep 13, 2002 at 02:42:14PM -0700, Earl Chew wrote: > I just stabilised a mips-vxworks (ELF) cross-debugger using gdb-5.0, and > rolled forward to gdb-5.2.1. Gdb-5.0 seems to work ok. But > I amazed to see 5.2.1 issue thousands of: > > warning: (Internal error: pc 0x89f21e10 in read in psymtab, but not > in symtab.) > > messages. I look at 0x89f21e10 in the VxWorks shell, and it > says: > > -> l 0x89f21e10 > testRanking(int,const char*) > 0x89f21e10 ... etc ... > > So this address contains the first instruction of a function. > > Does anyone know why gdb is issuing this warning, and why 5.0 was > ok with it? What debug information is produced by your toolchain - mdebug, I bet. Mdebug support is a little on the rotting side because we don't have anyone interested/willing to maintain it; and mdebug is a mighty arcane format. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer