Deadly embrace between pthread_cond_wait and pthread_cond_signal

Robert Collins robert.collins@itdomain.com.au
Wed Jun 27 19:19:00 GMT 2001


> -----Original Message-----
> From: Greg Smith [ mailto:gsmith@nc.rr.com ]
> Sent: Thursday, June 28, 2001 11:26 AM
> To: cygwin@cygwin.com
> Subject: Re: Deadly embrace between pthread_cond_wait and
> pthread_cond_signal
> 
> 
> Robert Collins wrote:
> 
> > Volume of calls :}. openening files doesn't occur quite as 
> often as (say)
>                       ^^^^^^^^^
> That might be easy for you to say !!

:]
 
> > I'd like to publicly thank Greg Smith for his excellent 
> profiling work in
> > identifying the bottleneck here. I know how time consuming 
> that can be :}.
> 
> That's all fine and dandy, what I wanna know is `When's the 
> check coming in
> the mail ?'  ;-)

Right after I get mine :].
 
> I do have another problem, which I think is associated with 
> pthread_kill,
> signals, and related ilk.
> 
> 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.
> 
> Soon as I can provide more details, I'll open a new thread ;-)

Please do. As Chris has already mentioned the signals code isn't
particulary thread capable right now. It's thread safe, but that's a
different thing. I don't know the signals code, but I'm happy to attempt
tweaks on it :}.

Rob

--
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/



More information about the Cygwin mailing list