> Maybe we have a futex problem in glibc on hppa? > In glibc nptl/pthread_mutex_trylock.c we check the return value of a futex syscall against EWOULDBLOCK. > Since on parisc - in contrast to all other architectures - we have EWOULDBLOCK!=EAGAIN, we maybe missed a check? That's a very interesting observation! The manpage doesn't say EWOULDBLOCK is a valid error return for FUTEX(2). I wonder is there are more slips like this. It looks like the same bug is present in nptl/sysdeps/unix/sysv/linux/sem_wait.c and nptl/sysdeps/unix/sysv/linux/sem_timedwait.c. This might explain my previous mail. Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
