Re: Parental Controls - [Was: NSTask Explodes. Clueless.]

2013-05-12 Thread Seth Willits
On May 12, 2013, at 6:47 PM, Ken Thomases wrote: > On May 12, 2013, at 8:08 PM, Seth Willits wrote: > >> The user running my main application has parental controls enabled. The user >> is allowed to run the main application, and can, but the helper task that is >> bundled inside the main applic

Re: Parental Controls - [Was: NSTask Explodes. Clueless.]

2013-05-12 Thread Ken Thomases
On May 12, 2013, at 8:08 PM, Seth Willits wrote: > The user running my main application has parental controls enabled. The user > is allowed to run the main application, and can, but the helper task that is > bundled inside the main application's bundle is not allowed to run. When the > *task*

Parental Controls - [Was: NSTask Explodes. Clueless.]

2013-05-12 Thread Seth Willits
Update: I *finally* got a bead on this. The user running my main application has parental controls enabled. The user is allowed to run the main application, and can, but the helper task that is bundled inside the main application's bundle is not allowed to run. When the *task* launches, *it*

Re: NSTask Explodes. Clueless.

2013-02-07 Thread Seth Willits
On Feb 6, 2013, at 10:29 PM, Chris Hanson wrote: > On Feb 4, 2013, at 11:26 AM, Seth Willits 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

Re: NSTask Explodes. Clueless.

2013-02-07 Thread Ivan Ostres
On 2/4/13 8:26 PM, Seth Willits wrote: [snip] Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.Foundation0x978142d8 ___NEW_PROCESS_COULD_NOT_BE_EXECD___ + 7 1 com.apple.Foundation0x976d2e16 -[NSConcreteTask launchWithDictionary:] + 4698 2

Re: NSTask Explodes. Clueless.

2013-02-06 Thread Chris Hanson
On Feb 4, 2013, at 11:26 AM, Seth Willits 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

Re: NSTask Explodes. Clueless.

2013-02-06 Thread Chris Hanson
On Feb 5, 2013, at 10:39 AM, Seth Willits wrote: >> Does your crash log show multiple threads? I would expect that the crash log >> shows only one thread because NSTask called fork() already. > > Hmm. Yes, there's only one thread. I didn't notice that. That explains the > crash (of the forked

Re: NSTask Explodes. Clueless.

2013-02-05 Thread Seth Willits
> Does your crash log show multiple threads? I would expect that the crash log > shows only one thread because NSTask called fork() already. Hmm. Yes, there's only one thread. I didn't notice that. That explains the crash (of the forked process) "instead of an exception," like you mentioned. >

Re: NSTask Explodes. Clueless.

2013-02-05 Thread Greg Parker
On Feb 4, 2013, at 11:26 AM, Seth Willits wrote: > Exception Type: EXC_BREAKPOINT (SIGTRAP) > Exception Codes: 0x0002, 0x > > *** NSTask: Task create for path > '/Applications/App.app/Contents/Resources/mytask' failed: 22, "Invalid > argument". Terminating temporary

NSTask Explodes. Clueless.

2013-02-04 Thread Seth Willits
In my app I have to launch background processes (bundled within my app's Resources folder) to do some things, and I launch them with NSTask. Every now and then I get a crash report which shows NSTask throws some fatal exception which is not caught by a wrapping @try block. For example: @tr