Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Bernardo Innocenti <bernie@develer.com>, gdb@sourceware.org
Subject: Re: could not find partial DIE in cache
Date: Mon, 28 Mar 2005 15:57:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0503280936590.4385@lazy> (raw)
In-Reply-To: <20050327154114.GA22514@nevyn.them.org>


Daniel,

Any chance that my patch will get a nod from the maintainers? I waiting
for approval to commit.

Thanks
-----
manjo
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cogito ergo sum                                                          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

On Sun, 27 Mar 2005, Daniel Jacobowitz wrote:

> On Sun, Mar 27, 2005 at 09:39:39AM +0200, Bernardo Innocenti wrote:
> > Hello,
> >
> > I've come across this internal-error:
> >
> > ---cut---
> > GNU gdb 6.3.0.20050323-cvs
> > Copyright 2004 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and you are
> > welcome to change it and/or distribute copies of it under certain
> > conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show warranty" for details.
> > This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db
> > library "/lib/tls/libthread_db.so.1".
> > (gdb) run
> > Starting program: /home/bernie/src/grs/display/display
> > ../../src-HEAD/gdb/dwarf2read.c:5446: internal-error: could not find
> > partial DIE in cache
> > ---cut---
> >
> > The bug also affects versions of GDB shipped by RedHat
> > (6.3.0.0-1.3rh and 6.1post-1.20040607.43rh).
> >
> > It happens with any application linked against libqt-mt.so.3.3.4,
> > when such library is built with -g or -ggdb2.  I'm using
> > a recent GCC 4.0 snapshot to build it.
>
> Normally, this error is a bug in GDB; there's one queued patch for a
> related problem, and I have another after that one is approved.
> However, in this case it is almost certainly a bug in GCC.  Does your
> snapshot include the fix for PR c++/19769?
>
> --
> Daniel Jacobowitz
> CodeSourcery, LLC
>


  parent reply	other threads:[~2005-03-28 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27  7:39 Bernardo Innocenti
2005-03-27 15:40 ` Daniel Jacobowitz
2005-03-27 23:44   ` Bernardo Innocenti
2005-03-27 23:48     ` Daniel Jacobowitz
2005-03-28 15:57   ` Manoj Iyer [this message]
2005-03-28 15:58     ` Daniel Jacobowitz

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=Pine.LNX.4.58.0503280936590.4385@lazy \
    --to=manjo@austin.ibm.com \
    --cc=bernie@develer.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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