This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: internal-error: could not find partial DIE in cache
- From: Daniel Jacobowitz <drow at false dot org>
- To: Manoj Iyer <manjo at austin dot ibm dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 1 Feb 2005 15:59:35 -0500
- Subject: Re: internal-error: could not find partial DIE in cache
- References: <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