Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Wed, 18 Apr 2001 19:51:07 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: pthread condition vars - Doh! Message-ID: <20010418195107.B6060@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <025701c0c861$e40e01c0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <025701c0c861$e40e01c0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Thu, Apr 19, 2001 at 09:46:52AM +1000 On Thu, Apr 19, 2001 at 09:46:52AM +1000, Robert Collins wrote: >I've just found out that SignalObjectAndWait, which I use in several >locations in the pthreads code, is not available on 9x platforms. >SignalObjectAndWait is the appropriate function to prevent races for >emulated posix objects that involve more than 1 win32 object. Yep. I have long wanted a SingalObjectAndWait for Cygwin's signal handling but I couldn't use it for this reason. I missed that you were using this in your new code. I assume that you'll be providing some kind of wrapper to handle this? cgf