Am 07.04.2010 18:29, schrieb Matthew Dillon:
> There might be another issue with signal races and fork(). The only
> two possible issues are programs ignoring ^C and a signal race in
> fork() (where the signal gets caught during the fork() but the
> child is then created and never gets the signal).
I've looked a bit at this with tuxillo and in our make's case it's -B
(compatMake == true) which exposes the buggy behavior.
compatMake is false when you use -j and true when you don't. As soon as
I run 'make -j 1 clean' it no longer fails.
Sascha
--
http://yoyodyne.ath.cx