• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 2.1: <incomplete type> in debugger??
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2.1: <incomplete type> in debugger??


  • Subject: Re: Xcode 2.1: <incomplete type> in debugger??
  • From: Justin Greenfield <email@hidden>
  • Date: Thu, 16 Jun 2005 16:18:17 -0500


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

I have the exact same problem.

I filed a bug about this (w/ source code) while at WWDC (radr: //4144739).  I think it was immediately assigned to the Apple engineer who was helping me in the xcode lab (I forget his name now).  From my source he generated the file that I included in my report.  He was able to compile it (with some special gcc magic, all foreign to me) and load it in the debugger and reproduce the problem.  

What is odd is that when stopping at a breakpoint in some parts of my code, a Foo* is <incomplete type> and in other parts of my code Foo* shows up as normal.  In some places I can't even view the value of a bool.  

This makes XCode pretty seriously broken for me, unfortunately.  I can't really use it on a day-to-day basis if I can't see even the standard types in the debugger.

Justin

 _______________________________________________
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

References: 
 >Xcode 2.1: <incomplete type> in debugger?? (From: Glen Simmons <email@hidden>)
 >Re: Xcode 2.1: <incomplete type> in debugger?? (From: Jim Ingham <email@hidden>)

  • Prev by Date: Re: Setting the selection of a document via AppleScript
  • Next by Date: YACWP (Yet Another CodeWarrior Port)
  • Previous by thread: Re: Xcode 2.1: <incomplete type> in debugger??
  • Next by thread: Re: GCC-XML for XCode?
  • Index(es):
    • Date
    • Thread