This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Mystified by "Internal error: pc 0x89f21e10 read in psymtab, but not in symtab
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Earl Chew <earl_chew at agilent dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 13 Sep 2002 18:01:10 -0400
- Subject: Re: Mystified by "Internal error: pc 0x89f21e10 read in psymtab, but not in symtab
- References: <3D825BB5.48CFAFAB@agilent.com>
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