From: Daniel Jacobowitz <drow@mvista.com>
To: Earl Chew <earl_chew@agilent.com>
Cc: gdb@sources.redhat.com
Subject: Re: Mystified by "Internal error: pc 0x89f21e10 read in psymtab, but not in symtab
Date: Fri, 13 Sep 2002 15:01:00 -0000 [thread overview]
Message-ID: <20020913220110.GA22097@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2002-09-13 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 14:42 Earl Chew
2002-09-13 15:01 ` Daniel Jacobowitz [this message]
2002-09-13 15:42 ` Earl Chew
2002-09-13 15:51 ` Daniel Jacobowitz
2002-09-13 16:13 ` Earl Chew
2002-09-13 18:32 ` Daniel Jacobowitz
2002-09-15 8:43 ` Earl Chew
2002-09-15 9:02 ` Daniel Jacobowitz
2002-09-15 9:11 ` Earl Chew
2002-09-15 13:39 ` H. J. Lu
2002-09-15 13:43 ` Daniel Jacobowitz
2002-09-15 21:42 ` Earl Chew
2002-09-16 7:03 ` H. J. Lu
2002-09-16 12:26 ` Jim Blandy
2002-09-16 13:01 ` Earl Chew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020913220110.GA22097@nevyn.them.org \
--to=drow@mvista.com \
--cc=earl_chew@agilent.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox