[lkml]   [2000]   [Aug]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [FIX] Make deadlock detection work for file locking
Andries Brouwer wrote:
> Generally POSIX error descriptions are not exhaustive.

Yes, I know ... the problem here is that it's not even clear what
should be considered to be an error, and "common sense" still
leaves a broad range of possibilities.

BTW, here's another threads problem (2.4.0-test7, glibc-2.1.3):

#include <unistd.h>
#include <pthread.h>

static void *thread(void *dummy)

int main(void)
pthread_t th;

while (1) {
return 0;

The _exit doesn't. Again, the description in POSIX.1 isn't as clear
as it could be (doesn't mention threads explicitly).

- Werner

/ Werner Almesberger, ICA, EPFL, CH /
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.041 / U:0.292 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site