Re: Xcode 2.1: <incomplete type> in debugger??
Re: Xcode 2.1: <incomplete type> in debugger??
- Subject: Re: Xcode 2.1: <incomplete type> in debugger??
- From: Jim Ingham <email@hidden>
- Date: Thu, 16 Jun 2005 13:56:42 -0700
Glen,
Thanks... You might also try switching the GCC_DEBUGGING_SYMBOLS to -
gfull. The default is -gused. These are two different ways of
reducing the size of debug info. If you are running into a compiler
bug, since the two optimizations take different paths through the
compiler/linker, you might luck out and -gfull bypasses the bug???
Not an answer, but worth a try anyway.
Jim
On Jun 16, 2005, at 1:35 PM, Glen Simmons wrote:
These are from the target. The blank ones were not bold, so I guess
they were the default. Here's the actual values:
ZERO_LINK = NO
SECTORDER_FLAGS =
DEAD_CODE_STRIPPING = NO
COPY_PHASE_STRIP = NO
GCC_GENERATE_DEBUGGING_SYMBOLS = YES
GCC_DEBUGGING_SYMBOLS = default
GCC_OPTIMIZATION_LEVEL = 0
So, no "dead code stripping" w/o -gfull. I'll see if I can get the
stuff below for you.
Thanks
Glen
On Jun 16, 2005, at 3:09 PM, Jim Ingham wrote:
<incomplete type> is the error that results when "something has
gone wrong and gdb can't figure out what the type of variable x
is". There are many possible causes, and there's unlikely to be
one workaround.
One common cause is that you turned on "dead code stripping" but
not -gfull. That can cause corruption in the debug info.
I actually can't tell from the build settings below whether this
is the case. I think you need to cut & paste them from the target
not the project? Anyway, if GCC_DEBUGGING_SYMBOLS really were "",
then you wouldn't get as far as <incomplete type> so those can't
be the whole story...
Anyway, if you can file a bug on it, that would be really
helpful. I have no way to tell what's going on or fix it without
more information.... To analyze the problem I need to get my
hands on a debug version of your project, the XCode-gdb transcript
of a run that got you to the point where you saw the <incomplete
type> error, and instructions on what I had to do with your app to
get it to that point.
I don't need sources or the Xcode project, just the debug
executable/framework/whatever... If your company is okay with
making that available, then please do file a bug with the
information mentioned above, and I will look into it.
Jim
On Jun 16, 2005, at 12:55 PM, Glen Simmons wrote:
OK, is there a workaround for <incomplete type> showing up in the
debugger? This is showing up for a local variable of type
CFStringRef, not something odd and exotic. Here's the relevant
build settings (being able to select multiple and copy is quite
cool, btw):
ZERO_LINK =
SECTORDER_FLAGS =
DEAD_CODE_STRIPPING =
COPY_PHASE_STRIP = NO
GCC_GENERATE_DEBUGGING_SYMBOLS =
GCC_DEBUGGING_SYMBOLS =
GCC_OPTIMIZATION_LEVEL = 0
Thanks,
Glen Simmons
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden