Re: Problems with pthread mutexes

Arash Partow wrote: > The result I get back is 16 which according to stderror is: "Mount device > busy". That would be EBUSY. > The mutex is being created within a running thread. It is very strange > that the same code compiles fine on other OS and that they don't give > back an error. > > I'l

Re: Problems with pthread mutexes

Hi Brian, The result I get back is 16 which according to stderror is: "Mount device busy". The mutex is being created within a running thread. It is very strange that the same code compiles fine on other OS and that they don't give back an error. I'll try writing up a more simpler example that ca

Re: Problems with pthread mutexes

Arash Partow wrote: > I've got a problem with pthread mutexes and cygwin. When I try to initialise > a mutex > attribute variable, the related pthread call never returns a 0 (zero) value. > > ie: > >int result = 0; >pthread_mutexattr_t mutex_attr; > >if ((result = pthread_mutexattr_

Problems with pthread mutexes

Hi all, I've got a problem with pthread mutexes and cygwin. When I try to initialise a mutex attribute variable, the related pthread call never returns a 0 (zero) value. ie: int result = 0; pthread_mutexattr_t mutex_attr; if ((result = pthread_mutexattr_init(&mutex_attr)) != 0) { pri