Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3B3A90B5.CD8E84C7@nc.rr.com>
Date: Wed, 27 Jun 2001 22:04:37 -0400
From: Greg Smith <gsmith AT nc DOT rr DOT com>
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Deadly embrace between pthread_cond_wait and pthread_cond_signal
References: <20010627023524 DOT S19058 AT redhat DOT com> <00aa01c0ff1b$44106960$a300a8c0 AT nhv> <20010627112321 DOT A21615 AT redhat DOT com> <037401c0ff5c$ed60ebc0$806410ac AT local> <3B3A86CF DOT DC0FA39A AT nc DOT rr DOT com> <3B3A87BB DOT 3F7AF46 AT nc DOT rr DOT com> <20010627212201 DOT A27163 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Well, I'm certainly not in a position to disagree (yet:-), but
our app has run just fine with Pthreads-win32 since last
Dec or Nov or so.  In fact, with our `Pthreads-win32 kluge' in
place, it runs just fine on Cygwin with today's patches!!
(See http://www.bsp-gmbh.com/hercules/herc_w32.html).

Any bets on I can't find the problem ;-)

I didn't ask to find Cygwin, I got there by serendipity.

We were quite happy running our app on linux and then some
enterprising souls figured out how to run it on Windows using
Cygwin and the Pthreads-win32 package.  As I told Rob last night
(which was today for him, but now he's in tomorrow;-), this
effectively doubled the participation for our app... (IOW you
have a great thing going on here), but this has added a whole
new dimension in that we have to get Cygwin to work with our app
(we can't stand whiny users ;-)

Since I have to run Windoze at work tho, I am thankful for being
turned on to Cygwin, and can't live w/o it.

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/