SenTestingKit, NSTask, and OBJC_DISABLE_GC
SenTestingKit, NSTask, and OBJC_DISABLE_GC
- Subject: SenTestingKit, NSTask, and OBJC_DISABLE_GC
- From: Andy Mroczkowski <email@hidden>
- Date: Wed, 8 Oct 2008 17:33:52 -0400
Hi everyone. This is a weird one, but I've hit a real roadblock here,
so any insight would really be appreciated.
I followed Chris Hanson's nice instructions for setting up a unit test
bundle for an application:
http://chanson.livejournal.com/120263.html
It all appears to be set up correctly. So as step 0, I build my new
unit testing target without actually adding any tests, just to make
everything is A-OK.
My application builds and runs fine, but doesn't start up as I
expect. After some investigation I find that the problem is related
to an NSTask it launches as part of the startup process. Its a basic
shell command whose output is just read into a string. However when
built and run through the testing bundle, the following output occurs
on stderr of my NSTask sub-process:
objc[37170]: GC: forcing GC OFF because OBJC_DISABLE_GC is set
objc[37170]: GC: forcing GC OFF because OBJC_DISABLE_GC is set
objc[37170]: GC: forcing GC OFF because OBJC_DISABLE_GC is set
This is throwing off the interpretation of the shell task output. I
don't want to just suppress stderr, because other useful information
could be present.
How do I suppress this "GC: forcing GC OFF because OBJC_DISABLE_GC is
set" so it won't appear in the stderr output of my NSTask?
Note, there are some similarities to these threads, but they don't
really address the issue I'm having:
http://www.cocoabuilder.com/archive/message/xcode/2008/7/12/23081
http://www.cocoabuilder.com/archive/message/xcode/2008/10/6/25055
halp.
- Andy
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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