Re: NSTask Explodes. Clueless.
Re: NSTask Explodes. Clueless.
- Subject: Re: NSTask Explodes. Clueless.
- From: Chris Hanson <email@hidden>
- Date: Wed, 06 Feb 2013 22:29:42 -0800
On Feb 4, 2013, at 11:26 AM, Seth Willits <email@hidden> wrote:
> Looking around the open source code for exec(), it appears EINVAL (22) can be returned if the task was exec()'d when not called from a vfork()'d process, with the comment /* If we're not in vfork, don't permit a mutithreaded task to exec */ which seems to line up with the *** multi-threaded process forked *** line in the crash log… trouble is I have no idea what this ultimately means to me. Seems like an OS bug?
One thing that occurs to me is that there might be something running that is injecting itself into your app's address space - and into the address space of the forked subprocess, and trying to do something "on startup."
What loaded libraries are listed in the crash dump?
-- Chris
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please 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