This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Deadly embrace between pthread_cond_wait and pthread_cond_signal
- To: cygwin at cygwin dot com
- Subject: Re: Deadly embrace between pthread_cond_wait and pthread_cond_signal
- From: Greg Smith <gsmith at nc dot rr dot com>
- Date: Wed, 27 Jun 2001 21:26:19 -0400
- References: <20010627023524.S19058@redhat.com> <00aa01c0ff1b$44106960$a300a8c0@nhv> <20010627112321.A21615@redhat.com> <037401c0ff5c$ed60ebc0$806410ac@local> <3B3A86CF.DC0FA39A@nc.rr.com>
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 ?' ;-)
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 ;-)
Greg
--
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/