IOV_MAX value

Hi, I am trying to compile the ACE framework on cygwin. One of the problem I have is that they are using arrays of size IOV_MAX on the stack. Since IOV_MAX is defined in limits.h as #define IOV_MAX (__INT_MAX__-1) that turns out to be problematic Looking on some other platforms I see that I

RE: pthread_mutex_trylock does not lock

Robert Collins wrote: > On Tue, 2002-12-03 at 23:06, Chris Knight wrote: > > Hello Rob, > > > > I have changed the code, see below. I now set the type to > > PTHREAD_MUTEX_NORMAL but that also does not block. The only documentation > > on cygwin threads say this is the same as PTHREAD_MUTEX_FAST_

Re: pthread_mutex_trylock does not lock

Robert Collins wrote: On Thu, 2002-12-05 at 08:33, Christophe Galerne wrote: NB: PT_MUTEX_NORMAL is not a posix mutex type - it's PTHREAD_MUTEX_NORMAL Right that was a typo. Or you could check the return value from pthread_mutexattr_settype and see that it returns EINVAL. The thi

Re: pthread_mutex_trylock does not lock

Robert Collins wrote: I never said that PTHREAD_MUTEX_NORMAL does not block, I was challenging the apparent 'cygwin threads' documentation. Right, in a way my remarq was OT... =:-D Christophe -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cy

[patch] Symbolic value for PTHREAD_MUTEX_DEFAULT

Hi, As discussed with Robert Collins, I propose this patch to make the 'default' mutex type more explicit. 2002-12-05 Christophe Galerne <[EMAIL PROTECTED]> * pthread.h (PTHREAD_MUTEX_DEFAULT): reorder PTHREAD_MUTEX_DEFAULT and PTHREAD_MUTEX_RECURSIVE so that PTHREAD_MUTE