On Sun, 10 Jul 2005 14:07:53 +1000, Robert Lunnon wrote:
OK, what do you mean the kernel doesn't allow you to do that - Suspend a thread or ??? Why not just write a SIGSTOP
SIGSTOP has process scope on NPTL, I think.
If SIGUSR1 isn't handled, then stuff will break mysteriously. Essentially all it does is block on a wineserver fd until the thread is woken up again. In future it'll also store the sigcontext so copy protection and such works.
thanks -mike