On Feb 4, 2013, at 11:26 AM, Seth Willits <sli...@araelium.com> 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 (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
