Deadly embrace between pthread_cond_wait and pthread_cond_signal

[Greg Smith]

Yes, you are absolutely correct.  Turns out pthread_kill() in the
Pthreads-win32 implementation is essentially a nop and we had changed
our select() in the thread that we want to signal to time-out when
we compile under windows.

So, I'm happy to say, this problem turned out to be a `personal problem' ;-)

Greg

Christopher Faylor wrote:

> >Seems we do a lotta SIGHUPs to break a listening thread out of his
> >reverie, but sometimes the wrong thead (which has done a recv() on a
> >socket) gets woken up instead, and is not particularly happy with the
> >EINTR error code.
> 
> Unless Robert has performed some magic that I'm not aware of, there is
> currently no way to interrupt anything but the main thread in cygwin.
> 
> This has been on my tuit list for a long time but it will require a
> lot of rework of the signal code.
>

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/