RE: 10.5 lauchctl unload causing process crash
RE: 10.5 lauchctl unload causing process crash
- Subject: RE: 10.5 lauchctl unload causing process crash
- From: "Carl Smith" <email@hidden>
- Date: Thu, 7 Feb 2008 09:47:09 -0800
- Thread-topic: 10.5 lauchctl unload causing process crash
The daemon was compiled on 10.4 xcode and is crashing with the call:
Sudo launchctl unload
/System/Library/LaunchDaemons/com.mycompany.mydaemon.com. from the
installer script.
It is the daemon crashing.
I am trying to debug it in xcode 3.0 and it seems to be crashing with a
EXE_BAD_ACCESS when the SIGTERM is sent by launchctl unload. I was
starting to think that this might be something with the way the project
is set up in 10.4 and possible do I need to do some changes in the xcode
project to pull in the correct/new headers or something.
The installer is pretty simple basically I have two background programs,
agent/daemon, and the installer checks to see if either is currently
installed and/or running shuts down if they are running and installs the
new programs. The installer is causing the daemon to crash on the unload
thus causing the rest of the installation to fail.
I thought I was reading where Apple had down some changes/beefing up of
the launchd program/procedure. Could this be affecting the 10.5 run?
Thanks
Carl
-----Original Message-----
Subject: Re: 10.5 lauchctl unload causing process crash
So which process is actually crashing? Is it th daemon or Installer.app
while some of your payload is running? It's pretty hard to debug without
knowing what your installer is calling? Shell scripts? Custom plugings?
Other tools?
Mike
Carl Smith wrote:
> I have an installer that works fine on 10.3 and 10.4. But now with
10.5
> out when I run the installer I am getting a crash at the launchctl
> unload call. It is reporting "Stray process with PGID equal to this
dead
> job: PID 324 PPID 1 installer" "Exited abnormally: Abort Trap" and so
on
> talking about the NSInvalidReceivedPortException.
>
>
>
> Basically what the installer does is stop the daemon if it is running
> and launches the new/updated one. But I am puzzled why there is not
this
> problem in 10.3 and 10.4.
>
>
>
> Any one have any suggestions?
>
>
>
> Thanks
>
> Carl
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden