mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-06 11:41:34 +00:00
20dc727851
The test code in drd/tests/trylock.c attempts to write-lock a POSIX rwlock twice. The code expects the second attempt to return an error, but POSIX doesn't require that behaviour, and FreeBSD's implementation deadlocks instead. See also https://bugs.kde.org/show_bug.cgi?id=403212 Reported-by: Mark Johnston <markj@FreeBSD.org>
21 lines
840 B
Plaintext
21 lines
840 B
Plaintext
|
|
Locking rwlock via pthread_rwlock_wrlock().
|
|
Locking rwlock via pthread_rwlock_trywrlock().
|
|
Locking rwlock via pthread_rwlock_timedwrlock().
|
|
Locking rwlock via pthread_rwlock_rdlock().
|
|
Locking rwlock via pthread_rwlock_tryrdlock().
|
|
Locking rwlock via pthread_rwlock_timedrdlock().
|
|
Attempt to lock for writing recursively (not allowed).
|
|
Recursive writer locking not allowed: rwlock 0x.........
|
|
at 0x........: pthread_rwlock_trywrlock (drd_pthread_intercepts.c:?)
|
|
by 0x........: main (trylock.c:?)
|
|
rwlock 0x........ was first observed at:
|
|
at 0x........: pthread_rwlock_init (drd_pthread_intercepts.c:?)
|
|
by 0x........: main (trylock.c:?)
|
|
|
|
Locking mutex via pthread_mutex_trylock().
|
|
Locking mutex via pthread_mutex_lock().
|
|
Locking mutex via pthread_mutex_timedlock().
|
|
|
|
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
|