I finished this if anyone's interested. it's all controlled by the
Info.plist file now. And you don't need an arbitrary argument to
notify the child that it should only run the app.
The child only uses execvp so there's no high-leve api used.
http://pastebin.com/1pH8dxuM
On Mon, Sep 13, 2010 a
One more note about this. It does work as expected. But I am going to
take out the dependency of having that hardcoded "1" parameter - which
the child looks for so it only runs the cocoa app. I'll probably
change it to use named pipes. Then it won't depend on having arguments
correct.
On Mon, Sep
Thanks for the suggestions!
Yeah sorry I was getting around to fixing that return NSApplication thing.
here's another version that avoids higher level framework usage..
http://pastebin.com/20W1ZD8r
Does that look better?
On Mon, Sep 13, 2010 at 1:38 AM, Ken Thomases wrote:
> On Sep 13, 2010,
On Sep 13, 2010, at 3:05 AM, aaron smith wrote:
> Thanks for pointing that I can't use high level frameworks in a child.
> I'll set up everything I need for the execvp call before the actual
> fork.
You haven't addressed the problem. I was not talking about the later fork(),
but the first one.
On Mon, Sep 13, 2010 at 3:05 AM, aaron smith
wrote:
> Thanks for pointing that I can't use high level frameworks in a child.
> I'll set up everything I need for the execvp call before the actual
> fork.
>
> AH! I totally missed that I need to use an int to store the child exit
> status info.
>
> H
Thanks for pointing that I can't use high level frameworks in a child.
I'll set up everything I need for the execvp call before the actual
fork.
AH! I totally missed that I need to use an int to store the child exit
status info.
Here's a version that works now..
http://pastebin.org/860040
Thank
On Sep 13, 2010, at 2:30 AM, aaron smith wrote:
> I'm working on a test to catch when an application crashes, and launch
> another executable (eventually crash reporter).
>
> I'm exhibiting strange behavior - whenever I quit the application
> normally, the information I'm getting back about what
Hey all, quick question.
I'm working on a test to catch when an application crashes, and launch
another executable (eventually crash reporter).
I'm exhibiting strange behavior - whenever I quit the application
normally, the information I'm getting back about what happened and why
it stopped is al
