This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Mystified by "Internal error: pc 0x89f21e10 read in psymtab, but not in symtab

From: Earl Chew <earl_chew at agilent dot com>
To: gdb at sources dot redhat dot com
Date: Fri, 13 Sep 2002 14:42:14 -0700
Subject: Mystified by "Internal error: pc 0x89f21e10 read in psymtab, but not in symtab
Organization: Agilent Technologies

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?

Earl

Follow-Ups:
- Re: Mystified by "Internal error: pc 0x89f21e10 read in psymtab, but not in symtab
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]