public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: Mark Gritter <Mark.Gritter@Sun.COM>
To: nobody@sources.redhat.com
Cc: gdb-prs@sources.redhat.com,
Subject: Re: gdb/1903: internal-error: could not find partial DIE in cache
Date: Tue, 17 Jan 2006 21:18:00 -0000	[thread overview]
Message-ID: <20060117211801.26717.qmail@sourceware.org> (raw)

The following reply was made to PR gdb/1903; it has been noted by GNATS.

From: Mark Gritter <Mark.Gritter@Sun.COM>
To: gdb-gnats@sources.redhat.com
Cc:  
Subject: Re: gdb/1903: internal-error: could not find partial DIE in cache
Date: Tue, 17 Jan 2006 13:11:00 -0800

 I have encountered this bug as well.  A release build (-g -O3) of one of 
 our programs compiled with gcc-3.2.3 triggers "internal-error: could not 
 find partial DIE in cache", but a debug build (-g O1) is fine.
 
 I reproduced the problem under the gdb-6.4.50.20060112 snapshot, as well 
 as the 6.4, 6.3, and 6.2.1 releases.
 
 I have not yet tried using a newer compiler release, as that could be 
 fairly disruptive, but I will give it a shot.
 
 Backtrace of gdb:
 
 #0  0x009737a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
 #1  0x009b2e59 in raise () from /lib/tls/libc.so.6
 #2  0x009b4882 in abort () from /lib/tls/libc.so.6
 #3  0x0808292a in internal_vproblem (problem=0xaa3fdc,
      file=0x8231f68 "../../gdb-6.4.50.20060112/gdb/dwarf2read.c", 
 line=5468,
      fmt=0x8232374 "could not find partial DIE in cache\n", 
 ap=0xbff892dc "")
      at ../../gdb-6.4.50.20060112/gdb/utils.c:794
 #4  0x08082abc in internal_verror (
      file=0x8231f68 "../../gdb-6.4.50.20060112/gdb/dwarf2read.c", 
 line=5468,
      fmt=0x8232374 "could not find partial DIE in cache\n", 
 ap=0xbff892dc "")
      at ../../gdb-6.4.50.20060112/gdb/utils.c:809
 #5  0x08082ae0 in internal_error (
      file=0x8231f68 "../../gdb-6.4.50.20060112/gdb/dwarf2read.c", 
 line=5468,
      string=0x8232374 "could not find partial DIE in cache\n")
      at ../../gdb-6.4.50.20060112/gdb/utils.c:818
 #6  0x0812d942 in find_partial_die_in_comp_unit (offset=0, cu=0x0)
      at ../../gdb-6.4.50.20060112/gdb/dwarf2read.c:5468
 #7  0x0812da54 in fixup_partial_die (part_die=0x884f2e8, cu=0xbff893d0)
      at ../../gdb-6.4.50.20060112/gdb/dwarf2read.c:5512
 #8  0x08128e92 in scan_partial_symbols (first_die=0xb4dacfc4,
      lowpc=0xbff893c4, highpc=0xbff893c8, cu=0xbff893d0)
      at ../../gdb-6.4.50.20060112/gdb/dwarf2read.c:1687
 #9  0x08128ac6 in dwarf2_build_psymtabs_hard (objfile=0x84373c8, mainline=0)
      at ../../gdb-6.4.50.20060112/gdb/dwarf2read.c:1507
 #10 0x08124791 in elf_symfile_read (objfile=0x84373c8, mainline=0)
      at ../../gdb-6.4.50.20060112/gdb/elfread.c:603
 #11 0x080e96c4 in syms_from_objfile (objfile=0x84373c8, addrs=0x8424920,
      offsets=0x843d6e4, num_offsets=0, mainline=1, verbo=0)
      at ../../gdb-6.4.50.20060112/gdb/symfile.c:828
 #12 0x080e9abc in symbol_file_add_with_addrs_or_offsets (abfd=0x84246f0,
      from_tty=0, addrs=0x0, offsets=0x0, num_offsets=0, mainline=1, flags=0)
      at ../../gdb-6.4.50.20060112/gdb/symfile.c:940
 #13 0x080e9d4a in symbol_file_add_from_bfd (abfd=0x84246f0, from_tty=0,
      addrs=0x0, mainline=1, flags=0)
      at ../../gdb-6.4.50.20060112/gdb/symfile.c:1039
 #14 0x080e9d98 in symbol_file_add_main_1 (args=0xbffa299b "./supervisor",
      from_tty=0, flags=0) at ../../gdb-6.4.50.20060112/gdb/symfile.c:1074
 #15 0x080e9d7b in symbol_file_add_main (args=0xbffa299b "./supervisor",
      from_tty=0) at ../../gdb-6.4.50.20060112/gdb/symfile.c:1068
 #16 0x080ff52e in catch_command_errors (
      command=0x80e9d68 <symbol_file_add_main>, arg=0xbffa299b 
 "./supervisor",
      from_tty=0, mask=6) at ../../gdb-6.4.50.20060112/gdb/exceptions.c:530
 #17 0x0807cb42 in captured_main (data=0x0)
      at ../../gdb-6.4.50.20060112/gdb/main.c:688
 #18 0x080ff4a7 in catch_errors (func=0x807c3c0 <captured_main>,
      func_args=0xbff8a8e0, errstring=0x81f82b8 "", mask=6)
      at ../../gdb-6.4.50.20060112/gdb/exceptions.c:515
 #19 0x0807d063 in gdb_main (args=0x6)
      at ../../gdb-6.4.50.20060112/gdb/main.c:843
 #20 0x0807c383 in main (argc=0, argv=0x0)
      at ../../gdb-6.4.50.20060112/gdb/gdb.c:35
 


             reply	other threads:[~2006-01-17 21:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 21:18 Mark Gritter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-01 19:35 drow
2006-01-20 21:08 Mark Gritter
2006-01-18  4:48 jimb
2006-01-18  4:45 jimb
2005-04-01 14:18 Daniel Jacobowitz
2005-04-01  4:38 warudkar

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=20060117211801.26717.qmail@sourceware.org \
    --to=mark.gritter@sun.com \
    --cc=gdb-prs@sources.redhat.com \
    --cc=nobody@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).