This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: sem_trywait returns EAGAIN (rather than returning -1 and setting errno)

I haven't done much work on the sem* functions to date, other than
keeping the functional.

Patches, as always, gratefully accepted. Post daemon merge I can do a
review of the sem* functions.

The problem should _not_ be endemic in the pthreads code, as I rewrote
nearly all the pthread* functions from the P1003.1 draft spec.


----- Original Message -----
From: "Christopher Faylor" <>
To: <>
Sent: Tuesday, February 26, 2002 5:13 PM
Subject: Re: sem_trywait returns EAGAIN (rather than returning -1 and
setting errno)

> On Mon, Feb 25, 2002 at 09:31:41PM -0500, Andrew T. Schnable wrote:
> >I was doing some pthreads/semaphore work and I tracked down a problem
> >in my code to a bug in sem_trywait.  Posix sem_trywait is defined as
> >returning -1 and setting errno to EAGAIN if the semaphore would have
> >blocked.  The cygwin implementation returns EAGAIN an leaves errno
> >unchanged.
> >
> >Has anyone else encountered this problem and provided a fix?
> Hmm.  Unless I am missing something, it looks like this problem is
> prevalent in the pthreads code.  It makes me think that maybe the
> author meant to catch these kinds of things in the interface between
> the __pthread/pthread calls.
> Robert, can you explain what's going on here?
> cgf

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]