This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug nptl/300] pthread_cond_timedwait does not reacquire the mutex on cancelation
- From: "jakub at redhat dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 6 Aug 2004 15:13:11 -0000
- Subject: [Bug nptl/300] pthread_cond_timedwait does not reacquire the mutex on cancelation
- References: <20040805081906.300.sebastien.decugis@ext.bull.net>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From jakub at redhat dot com 2004-08-06 15:13 -------
I have been able to reproduce this on 8way and 4way P4, but haven't been able
to reproduce it on x86_64 (4way and 1way) and ia64 (4way).
Also, if pthread_cond_wait instead of pthread_cond_timedwait is used, I can't
reproduce it either (but I haven't ever seen the thread to hit ETIMEDOUT
in pthread_cond_timedwait, so both pthread_cond_wait and timedwait should behave
the same).
Which means the suspect is
nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=300
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.