wireguard-openbsd/regress/lib/libpthread/pthread_mutex, branch master WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/regress/lib/libpthread/pthread_mutex?h=master 2012-03-24T21:39:10Z Another tiny test case 2012-03-24T21:39:10Z guenther guenther@openbsd.org 2012-03-24T21:39:10Z urn:sha1:a86e12601c48964dcb48dcb3911589cd71332213 Check that PTHREAD_MUTEX_NORMAL mutexes will self-deadlock and that 2012-02-23T07:54:40Z guenther guenther@openbsd.org 2012-02-23T07:54:40Z urn:sha1:078d8877282ca7ebe0a00eb1e91b01d250b79bbf pthread_mutex_timedlock() will block and then timeout on self-deadlock Round-robin behavior isn't guaranteed by SCHED_OTHER and the kernel 2012-02-20T04:43:49Z guenther guenther@openbsd.org 2012-02-20T04:43:49Z urn:sha1:c9c91f29a90fba4da1fa8523047d09d6114a8877 doesn't have SCHED_FIFO or SCHED_RR support, so use sleep(1) to 'ensure' the second thread gets the lock when expected Add a test for recursive pthread_mutex_trylock() 2011-09-23T10:39:08Z uwe uwe@openbsd.org 2011-09-23T10:39:08Z urn:sha1:18bdda7b9a2c31e01546c749364c0c096f9853d7 ok guenther@ after mutex_unlock, there's no guarantee that a waiting thread will 2005-12-19T05:22:57Z tedu tedu@openbsd.org 2005-12-19T05:22:57Z urn:sha1:308936c60926c83fd0d04c15930f58acf8774352 start running. calling pthread_yield makes test pass with rthreads -Wall cleanup. 2005-10-30T23:59:43Z fgsch fgsch@openbsd.org 2005-10-30T23:59:43Z urn:sha1:d0774bb2f04aa46ef0bdd42b0257c67ce679eb9b various cleanups; david says results are same 2003-07-31T21:48:02Z deraadt deraadt@openbsd.org 2003-07-31T21:48:02Z urn:sha1:db3296cf5c1dd9058ceecc3a29fe4aaa0bd26000 convert everything to bsd.regress.mk 2002-01-03T00:43:47Z art art@openbsd.org 2002-01-03T00:43:47Z urn:sha1:3a3fbb3f2e2521ab7c4a56b7ff7462ebd9095ec5 Fix pthread_mutex regression test... undefined behavior does not 2001-11-03T04:33:48Z marc marc@openbsd.org 2001-11-03T04:33:48Z urn:sha1:523ac096323730620ac3e8254f0f0e574ac95f97 mean != EPERM in one test, minor changes to recursive mutex test. remove printf in signal test signal handler, run test long enough to ensure signal hander is called at least twice, reduce output. Note: running these tests over a remote console may indicate bogus falures due to console output latency. Any test that takes longer than 5 seconds to complete may be flagged as a failure. per man page and gcc 3.0.1, exit requires prototype from stdlib.h 2001-09-20T16:43:15Z todd todd@openbsd.org 2001-09-20T16:43:15Z urn:sha1:8445c53715e7030056b779e8ab40efb7820981f2