| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Jan 31, 2006, at 9:23 PM, Daniel Jalkut wrote:
I believe that usually these internal Xcode errors are triggered by -[NSException raise] in the source code. You may be able to set a breakpoint (yes, with gdb attached to Xcode) and gather clues. I admit this is a somewhat gallant effort to ask of a developer, but if you're curious and really determined not to lose your project and start from scratch, it may be your only choice.
I have used a combination of gdb debugging and manual editing of project files to repair situations like this before. Best of course is if you have a backup copy of the project file before the corruption occurred. You might find my blog entry on the subject of debugging an Xcode error dialog:
http://www.red-sweater.com/blog/67/xcode-search-gone-mad
Either inspiring or discouraging :)
Or you could send us the bad project file, we'll take a look at it, see what's wrong, and probably fix it and send it back to you.
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
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: http://lists.apple.com/mailman/options/xcode-users/email@hidden This email sent to email@hidden
| References: | |
| >Re: Xcode project hosed? (From: Chris Espinosa <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.