There are a bunch of changes/bugs in the version of gcc4 that's part
of Xcode 2.1 which are causing this failure. Usually, you can make
the situation much better (though there are still a few known
problems) by switching the debug level to -gfull, and rebuilding.
This can make the compile slower, but it will usually work around the
<incomplete type> errors.
Also, what tends to be broken is not the debugger's knowledge of the
type itself, but the link in the debug info from the variable to it's
type. So you can often see the value by casting the variable back to
its type in the Expressions window.
We will have this sorted out by the next release.
Jim
N.B. Sometimes this is a legit. message, usually because you have an
opaque pointer. But I assume you've already ruled out that possibility.
Jim
On Oct 5, 2005, at 8:39 AM, email@hidden wrote:
Hello all,
Has anyone else seen the <incomplete type> message when trying to view
variables in xcode? Is this a bug in Xcode and if so, is there a
workaround?
I am using Xcode 2.1 and have full debug symbols.
Regards,
Miles Henderson
OSX Engineer
Raining Data UK
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
