From: Michael Eager <eager@eagercon.com>
To: gdb@sources.redhat.com
Subject: GDB internal error: pc in psymtab, not in symtab
Date: Thu, 12 Oct 2006 04:29:00 -0000 [thread overview]
Message-ID: <452DC493.40908@eagercon.com> (raw)
I've been bitten by this same problem:
http://sourceware.org/ml/gdb/2005-11/msg00279.html
It looks like GDB issues a warning when the ELF symbol
table contains symbols, but the DWARF data doesn't.
Assembler source with a .file will have DWARF sections,
but only a TAG_Compilation_Unit. It's legit DWARF.
There seem to be fixes for problems with similar
symptoms with mdebug and stabs, but nothing for DWARF.
Have you seen any kind of fix?
Any suggestion for a fix? It doesn't look like GDB
knows where the debug info came from. One fix is
to simply suppress the message. Another is to have
the DWARF reader tag the psym if no symbols are found,
so that symtab.c can know that it's not an error.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next reply other threads:[~2006-10-12 4:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 4:29 Michael Eager [this message]
2006-10-12 4:43 ` Daniel Jacobowitz
2006-10-12 7:55 ` Steven Johnson
2006-10-12 12:52 ` Daniel Jacobowitz
2006-10-12 20:30 ` Steven Johnson
2006-10-12 15:11 ` Michael Eager
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=452DC493.40908@eagercon.com \
--to=eager@eagercon.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