in reply to Re: Is this a bug of perl threads?
in thread SOLVED: Is this a bug of perl threads?

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.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"I'd rather go naked than blow up my ass"

Replies are listed 'Best First'.
Re^3: Is this a bug of perl threads?
by Ray.Zachary (Acolyte) on Mar 12, 2010 at 02:49 UTC

    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.

    Yes, that's what I mean.

[reply]

      I don't know enough about socket comms on *nix, but can't accept return without a connection? For example, with ECONNABORTED.

      As all your server threads are using (cloned copies of) the same server socket backed by the same physical resource, is it possible that if one client aborts its connection, that could cause all your threads to receive that error from the accept, causing their while loops to terminate?

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
Re^3: Is this a bug of perl threads?
by ikegami (Patriarch) on Mar 12, 2010 at 02:59 UTC
    No idea what I was thinking.
[reply]

In Section Seekers of Perl Wisdom