Andrew T. Schnable [mailto:[EMAIL PROTECTED]] wrote:
> I think all the sem_* functions are broken similarly. [ ... ]
I just came across this myself while working on enabling
Cygwin Python threads. You may find the following function
helpful:
static int
fix_status(int status)
{
return (st
> -Original Message-
> From: Andrew T. Schnable [mailto:[EMAIL PROTECTED]]
> returning -1 and setting errno)
>
>
> I think all the sem_* functions are broken similarly. I have
> the threads.cc file modified
> and was going to try and submit patches, but I am having some
> issues g
>
To: <[EMAIL PROTECTED]>
Cc: "Andrew T. Schnable" <[EMAIL PROTECTED]>
Sent: Thursday, February 28, 2002 8:55 AM
Subject: RE: sem_trywait returns EAGAIN (rather than returning -1 and setting errno)
FWIW, I've patched sem_trywait and sem_wait. I haven't looked
FWIW, I've patched sem_trywait and sem_wait. I haven't looked for further cases of
misbehaviour though.
Rob
> -Original Message-
> From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
> As Robert indicated, in the vast majority of those cases,
> this was, in fact, the right thing to d
cool - I misunderstood. I will try and work up a patch...
Andy
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 26, 2002 7:33 PM
Subject: Re: sem_trywait returns EAGAIN (rather than returnin
On Tue, Feb 26, 2002 at 07:14:35PM -0500, Andrew T. Schnable wrote:
>You have a point regarding errno, but unfortunately, this is how the
>standard
>is written. If it's intentional that cygwin deviate from posix 1.b, I'm fine
>with that - I can code accordingly. FYI - I went to the
>
>The Ope
lt;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 26, 2002 5:19 PM
Subject: Re: sem_trywait returns EAGAIN (rather than returning -1 and
setting errno)
> On Wed, Feb 27, 2002 at 09:08:54AM +1100, Robert Collins wrote:
> >
> >
> >> -Original M
On Wed, Feb 27, 2002 at 09:08:54AM +1100, Robert Collins wrote:
>
>
>> -Original Message-
>> From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
>
>> 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 rewr
> -Original Message-
> From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
> 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.
>
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
return ETIMEDOUT;
return EAGAIN;
return EFAULT;
ret
tions from the P1003.1 draft spec.
Rob
===
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
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 cygw
12 matches
Mail list logo
