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:
I was trying to set the build settings to a debug version
(undocumented and
not available on imported codewarrior projects). Not sure why but
I now get
this error:
Path should be a non-empty string, but it's an empty string.
My options are to Quit or to continue where the same repeats
infinitely.
I've tried a full clean and did a repair permission. Still no luck.
Any suggestions. I'd rather not lose the entire project.
Thanks.
_______________________________________________
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/jalkut%40red-
sweater.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:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
