If anything, the bug is on the Windows side. One could say Perl is handling the Ctrl-C as if it was emulating a process even when it's not.
I read the OP to mean that he was interupting a client with ^C and that was having the side-effect of causing the server to terminate.
With the only connection between the interupted client and the threaded server being a socket, I doubt that the ^C is being 'forwarded' to it.
In reply to Re^2: Is this a bug of perl threads?
by BrowserUk
in thread SOLVED: Is this a bug of perl threads?
by Ray.Zachary
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |