in reply to Re: Non-blocking I/O woes
in thread Non-blocking I/O woes

Thanks! That was it - somehow I never expected can_read() to return with an empty handle array upon receiving a signal. But it does and it really explains everything: the silent exit and the erratic behavior and all that. Now that I got this mystery solved I'm happy and productive again. :)