I mentioned something similar for a different reason. Go look at the last
part of the following message in the recent -hackers archives:
> Subject: ptrace bug?
> MessageId: <[EMAIL PROTECTED]>
(this was for -stable, BTW)
Having the suspend for the ptrace()ing parent done in issignal is a pain
Maybe this should be in -arch.. I couldn;t make my mind up,
but..
There is some behaviour in signals which seems
1/ un-neccesary
2/ potentially dangerous.
in addition it is
3/ Definitly incompatible with KSEs.
I am hoping that someone can give me a good reason why it is done, and
failing that,
