From: Steven Johnson <sjohnson@sakuraindustries.com>
To: Michael Eager <eager@eagercon.com>, gdb@sources.redhat.com
Subject: Re: GDB internal error: pc in psymtab, not in symtab
Date: Thu, 12 Oct 2006 07:55:00 -0000 [thread overview]
Message-ID: <452DF4D9.607@sakuraindustries.com> (raw)
In-Reply-To: <20061012044310.GA21442@nevyn.them.org>
I suggest you read this thread:
http://sourceware.org/ml/gdb/2006-06/msg00085.html
It may be the cause of your problem, as it is the cause of this warning
for me.
I simply comment out the code referred to in this post and this warning
goes away for me. I can't come up with a better way to deal with it.
Of course if you also have .linkonce sections in your program, you are
probably hosed.
Steven J
Daniel Jacobowitz wrote:
> On Wed, Oct 11, 2006 at 09:29:07PM -0700, Michael Eager wrote:
>
>> 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.
>>
>
> Psymtabs do not come from the ELF symbol table; they come from a first
> pass over the DWARF information. So, if this warning triggers, that
> pass must have done something bogus.
>
> "maint print psymbols" and "maint print symbols" might be useful;
> the interesting question is, what psymtab thought it covered the
> address, and why didn't the corresponding symtab?
>
> Oh, one frequent cause is mis-estimating the range of addresses covered
> by the psymtab.
>
>
next prev parent reply other threads:[~2006-10-12 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 4:29 Michael Eager
2006-10-12 4:43 ` Daniel Jacobowitz
2006-10-12 7:55 ` Steven Johnson [this message]
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=452DF4D9.607@sakuraindustries.com \
--to=sjohnson@sakuraindustries.com \
--cc=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