Re: CFMessagePort problems
Re: CFMessagePort problems
- Subject: Re: CFMessagePort problems
- From: Paul Kim <email@hidden>
- Date: Mon, 4 Dec 2006 14:11:58 -0500
On Dec 4, 2006, at 1:54 PM, Chris Parker wrote:
Paul, Are you launching another copy of your command line program
by using fork() without a corresponding exec()? That might or might
not work depending on what's going on in the process at any given
time.
Cocoa requires an exec in order get all the various state into
shape for a new process - if you're not calling exec() you're going
to get strange behavior.
APEs and/or input managers certainly could exacerbate the situation.
.chris
--
Chris Parker
Cocoa Frameworks
Apple Computer, Inc.
No fork() or exec(). It's started by launchd. It does it's job then
quits until it's started by launchd again (either via a scheduled run
or triggered from a watch path). There are times that NSTask is used
though.
From the logs I've seen from users, it seems as if from a certain
point onwards, every invocation of the program is affected, as if
some switch was turned on to break everything. It leads me to believe
there's an external factor at play but it would be nice to know what
it is.
Thanks for the response. If there's anything else I can look at, let
me know.
Paul Kim
------------------------------------
Chief Noodler - Noodlesoft
email@hidden
http://www.noodlesoft.com
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden