Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com content-class: urn:content-classes:message Subject: RE: sem_trywait returns EAGAIN (rather than returning -1 and setting errno) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Wed, 27 Feb 2002 09:08:54 +1100 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: sem_trywait returns EAGAIN (rather than returning -1 and setting errno) Thread-Index: AcG+4P8IJjLXQEQuRu6JeE01zxriXgAMH1Gg From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g1QM9OR07186 > -----Original Message----- > From: Christopher Faylor [mailto:cgf@redhat.com] > On Tue, Feb 26, 2002 at 08:37:35PM +1100, Robert Collins wrote: > >The problem should _not_ be endemic in the pthreads code, as > I rewrote > >nearly all the pthread* functions from the P1003.1 draft spec. > > % grep 'return E' thread.cc *Sigh*. That just shows that that is what the code is meant to do. If you check the spec, you'll see that most of the pthread functions are meant to return the error number. i.e. picking a function at random - pthread_mutex_lock " RETURN VALUE If successful, the pthread_mutex_lock( ) and pthread_mutex_unlock( ) functions shall return zero; otherwise, an error number shall be returned to indicate the error. " 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/