* internal-error: could not find partial DIE in cache
@ 2005-02-01 20:53 Manoj Iyer
2005-02-01 20:59 ` Daniel Jacobowitz
0 siblings, 1 reply; 2+ messages in thread
From: Manoj Iyer @ 2005-02-01 20:53 UTC (permalink / raw)
To: gdb
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?
Really appriciate your input.
-----
manjo
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cognito ergo sum +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: internal-error: could not find partial DIE in cache
2005-02-01 20:53 internal-error: could not find partial DIE in cache Manoj Iyer
@ 2005-02-01 20:59 ` Daniel Jacobowitz
0 siblings, 0 replies; 2+ messages in thread
From: Daniel Jacobowitz @ 2005-02-01 20:59 UTC (permalink / raw)
To: Manoj Iyer; +Cc: gdb
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-02-01 20:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-02-01 20:53 internal-error: could not find partial DIE in cache Manoj Iyer
2005-02-01 20:59 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox