2003-October Archive by Thread
Messages are ordered newest-to-oldest in this index. The newest
threads will be at the top of this page, the oldest will be at the bottom.
Within a single thread, the first mail note is the START of the
thread; the notes following that are in the chronological order of
when they were received. So globally, newest messages are at the top,
but within a thread, the oldest (the start of the thread) is at the
top.
If you think about it, it is confusing. Just go with the flow and everything will be all right.
- NPTL: pthread_condtimedwait hang or mutex_lock hang,
srikrish
- NPTL kernel == kernel with TLS?,
R CHAN
- mozilla and nptl,
Rogelio M.Serrano Jr.
- binutils version,
Rogelio M.Serrano Jr.
- bits/stdio-lock.h,
Greg Schafer
- #define PTHREAD_BARRIER_SERIAL_THREAD EWOULDBLOCK,
Alexander Terekhov
- Mutex, Take 3 (for "dumb" futex),
Alexander Terekhov
- "lock_futex",
Alexander Terekhov
- Re: Trouble building current CVS libc on RH9,
Dan Kegel
- Bug with fcntl(n, F_SETOWN, getpid) with NPTL 0.34,
David Holmes
- PATCH - tst-cancelx7,
Greg Schafer
- Extending nptl's libthread_db.so interfaces for locking,
Howell, David P
- Question about pthread_cond_broadcast,
Bill Spitzak
- no more sources drops,
Ulrich Drepper
- Bug in i386 pthread_once implementation,
Daniel Jacobowitz
- Re: nptl 0.60,
Ulrich Drepper
- condvar performance in .59 vs .60,
Boris Kolpackov