From: Daniel Jacobowitz <drow@false.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: gdb@sources.redhat.com
Subject: Re: internal-error: could not find partial DIE in cache
Date: Tue, 01 Feb 2005 20:59:00 -0000 [thread overview]
Message-ID: <20050201205934.GA18544@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0502011343240.8178@lazy>
On Tue, Feb 01, 2005 at 01:45:58PM -0600, Manoj Iyer wrote:
>
> It will be a big help if I can get some inputs as to how I should go
> further on this problem.
>
> I have an executable compiled with IBM xlC++ compiler, when I run this
> program through GDB (RHEL 4, gdb 6.3) it throws and internal error :
>
> dwarf2read.c:5452: internal-error: could not find partial DIE in cache
>
> looking at the code, find_partial_die_in_comp_unit() is printing this
> message. libiberty/hashtab.c: htab_find_with_hash() function is returning
> an EMPTY_ENTRY.
>
> I dont know the internal of GDB enough. What should I be looking for? Is
> this because the hash table was created wrong or xlC produced some bad
> debug information. How do I find out?
Debug it :-) The hash table is created by scanning all DIEs. Is the
index being looked up a valid DIE? If so, why was it skipped?
--
Daniel Jacobowitz
prev parent reply other threads:[~2005-02-01 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 20:53 Manoj Iyer
2005-02-01 20:59 ` Daniel Jacobowitz [this message]
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=20050201205934.GA18544@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.ibm.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