This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug linuxthreads/6508] Problem with mutexes and semaphores
- From: "jakub at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 12 May 2008 22:41:00 -0000
- Subject: [Bug linuxthreads/6508] Problem with mutexes and semaphores
- References: <20080512221032.6508.bugreport@netmasters.cz>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From jakub at redhat dot com 2008-05-12 22:40 -------
Oops, sorry, that response was just to the comment, the testcase really doesn't
lock in one thread and unlock in a different one.
But, there are no guarantees both threads will alternate in the critical section
either, both threads have the same priority and thus it is arbitrary which one
acquires the mutex. As pthread_mutex_lock is called immediately after unlock,
there is high probability the same thread will acquire the lock again.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6508
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.