Re: xcode 2.2 beachball of death
Re: xcode 2.2 beachball of death
- Subject: Re: xcode 2.2 beachball of death
- From: Scott Ribe <email@hidden>
- Date: Sat, 03 Dec 2005 12:43:48 -0700
- Thread-topic: xcode 2.2 beachball of death
> As a workaround, it seems that if your final for statement has it's
> closing ')',
Well, heck, I hadn't been bitten by this since moving to 2.2, so I thought
maybe it had been fixed in the latest release of GCC. Is the OP specifying
an earlier compiler?
Anyway, the problem is that when using Objective-C++, the compiler hangs on
many forms of unterminated statements. The missing ')' in the for statement
of the OP's example, but also missing '}' in functions. I'd dug into it
enough to note that using top shows that the process eating up all the CPU
is objcpp (IIRC the exact name). Also note that if you leave it running too
long, all hell will eventually break loose, because objcpp is writing to a
log file the whole time. I once went out to run errands and left it running,
just to see if it would *ever* terminate, and it filled up my disk, which
had >120GB free before I started the build.
Oh, you can kill the offending objcpp instance from the command line and not
lose your current XCode session. XCode may deal more or less gracefully with
the compiler being killed out from under it (you may sometimes have to quit
and restart to get building to work again), but at least you won't lose your
current unsaved edits.
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 665-7007 voice
_______________________________________________
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