Re: [FIX] Make deadlock detection work for file locking

From: Werner Almesberger (almesber@lrc.epfl.ch)
Date: Fri Aug 25 2000 - 10:27:06 EST


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)
{
    _exit(0);
}

int main(void)
{
    pthread_t th;

    pthread_create(&th,NULL,&thread,NULL);
    while (1) {
        write(1,".",1);
        sleep(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       werner.almesberger@ica.epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 21:00:16 EST