From: Daniel Jacobowitz <drow@false.org>
To: Bernardo Innocenti <bernie@develer.com>
Cc: gdb@sourceware.org
Subject: Re: could not find partial DIE in cache
Date: Sun, 27 Mar 2005 23:48:00 -0000 [thread overview]
Message-ID: <20050327234850.GA1738@nevyn.them.org> (raw)
In-Reply-To: <42474588.7020809@develer.com>
On Mon, Mar 28, 2005 at 01:45:12AM +0200, Bernardo Innocenti wrote:
> Daniel Jacobowitz wrote:
> >On Sun, Mar 27, 2005 at 09:39:39AM +0200, Bernardo Innocenti wrote:
> >
> >>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.
>
> Could you please give a pointer to these patches?
> I'm eager to test them.
One was posted earlier this month by Manoj; the other hasn't been
posted yet (been too busy...)
> >However, in this case it is almost certainly a bug in GCC. Does your
> >snapshot include the fix for PR c++/19769?
>
> It most probably didn't: the patch was applied to the 4.0
> branch on 2005-03-23.
>
> Yesterday's fedora-devel pakages for GCC 4.0 list this PR
> as fixed in the RPM ChangeLog:
>
> * Thu Mar 24 2005 Jakub Jelinek <jakub@redhat.com> 4.0.0-0.36
> - update from CVS
> - PRs c++/19769, c++/19980, c++/20147, c++/20147, c++/20461, c++/20463,
Yes, that's the one you need.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-27 23:48 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 [this message]
2005-03-28 15:57 ` Manoj Iyer
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=20050327234850.GA1738@nevyn.them.org \
--to=drow@false.org \
--cc=bernie@develer.com \
--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