apr-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 45248] testlockperf of apr_thread_rwlock_t stalls forever on i686 Linux / glibc 2 .7
Date Sun, 29 Jun 2008 21:12:06 GMT

--- Comment #12 from Bojan Smojver <bojan@rexursive.com>  2008-06-29 14:12:05 PST ---
> The patch doesn't cause anything to be printed.

Right. This suggest we don't have any lock/unlock attempt failures in the

The manual page for pthread_rwlock_wrlock() function claims:
The pthread_rwlock_wrlock() function shall apply a write  lock  to  the
read-write  lock  referenced by rwlock. The calling thread acquires the
write lock if no other thread (reader or writer) holds  the  read-write
lock rwlock. Otherwise, the thread shall block until it can acquire the
lock. The calling thread may deadlock if at the time the call  is  made
it holds the read-write lock (whether a read or write lock).

Is is possible that the thread calling the locking routine is holding that lock

Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail: bugs-unsubscribe@apr.apache.org
For additional commands, e-mail: bugs-help@apr.apache.org

View raw message