setuuid/setguuid

René J.V. Bertin rjvbertin at gmail.com
Wed Dec 24 02:27:45 PST 2014


On Wednesday December 24 2014 21:16:54 Ian Wadham wrote:

Morning!

> The code always seems to work OK if the crash procedure in the failed
> program starts Dr Konqi by forking.  But it never works (on Apple OS X)
> if the crash procedure contacts an independent process (kdeinit4) via
> a socket and asks kdeinit4 to run Dr Konqi.  Starting via kdeinit4 is
> preferred to forking, in case the crashed program has a corrupted
> heap or whatever.

And all that DrKonqi really does is starting and stopping the crashed process via signals, and spawning a debugger with the necessary arguments for it to connect to the target process.

> i.e. the crashing program, Dr Konqi and kdeinit4.  That's the silly thing
> about this situation.  OS X won't let Dr K set privileges it already has.

Without having really looked at the code, have you tried NOT doing that (possibly after checking whether it has the required privileges)?

R.


More information about the macports-dev mailing list