From: Daniel Jacobowitz <drow@false.org>
To: Craig Jeffree <craig.jeffree@preston.net>
Cc: Jim Blandy <jimb@redhat.com>, gdb@sources.redhat.com
Subject: Re: <incomplete type>
Date: Mon, 12 Sep 2005 01:34:00 -0000 [thread overview]
Message-ID: <20050912013403.GA10666@nevyn.them.org> (raw)
In-Reply-To: <1125990841.25254.62.camel@norman>
On Tue, Sep 06, 2005 at 05:14:01PM +1000, Craig Jeffree wrote:
> > Failing that, could you post the readelf output for the entire
> > compilation unit containing Soi::Waypoint? From the compilation unit
> > header all the way down to the next one.
> >
>
> Yes. However, Daniel, Jim, I will send this to you privately as my
> company wishes to keep it off the public archives. I will send it in a
> separate email.
>
> Thanks for helping me through this.
First of all, I note that you're using GCC 3.2.3. That version didn't
output proper DWARF debugging information for namespaces, so it
triggers a different path through GDB (that involves a lot more
guessing).
Here's what I think is happening.
There's considerable code in GDB to guess the namespace of a structure
when this problem is encountered. But that code relies upon the
mangled names of member functions of the type. Probably it is
successfully triggering for the _definition_ of the type, but in some
other compilation unit (the one with the reference that shows up as
incomplete), the DIE containing the declaration of Soi::Waypoint
doesn't have enough information. So the best GDB can come up with is
"Waypoint". Then it looks, and doesn't find Waypoint - the only
definition was Soi::Waypoint, with a namespace qualifier. So, no
match.
There's just nothing GDB can do, if that's what's happening. You may
be able to find a GCC patch in the archives of gcc-patches or
gdb-patches to add DW_AT_namespace support to GCC 3.2.3, if rebuilding
the compiler is an option. Otherwise you're stuck until you upgrade
GCC.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-12 1:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 2:06 Craig Jeffree
2005-08-26 19:04 ` Jim Blandy
2005-08-29 7:50 ` Craig Jeffree
2005-08-29 18:38 ` Jim Blandy
2005-09-01 23:55 ` Craig Jeffree
2005-09-02 0:22 ` Jim Blandy
2005-09-02 1:50 ` Craig Jeffree
2005-09-02 13:16 ` Daniel Jacobowitz
2005-09-05 7:34 ` Craig Jeffree
2005-09-05 14:00 ` Daniel Jacobowitz
2005-09-06 7:15 ` Craig Jeffree
2005-09-12 1:34 ` Daniel Jacobowitz [this message]
2005-09-15 5:12 ` Craig Jeffree
2005-09-19 7:44 ` Craig Jeffree
2005-09-12 1:35 ` Daniel Jacobowitz
2005-09-02 2:05 ` Craig Jeffree
-- strict thread matches above, loose matches on Subject: below --
2005-05-01 21:21 "Incomplete Type" lin q
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=20050912013403.GA10666@nevyn.them.org \
--to=drow@false.org \
--cc=craig.jeffree@preston.net \
--cc=gdb@sources.redhat.com \
--cc=jimb@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).