drochner 6e71fa2242 add a test which exercises libpthread's ability to remember the ... threads which were created, doing some random mallocs in between so that threads are not equidistant in the address space (bug fixed in libpthread/pthread.c rev. 1.109)		2009-04-02 12:58:44 +00:00
..
atexit
barrier1	Print return value on error	2007-12-03 17:59:45 +00:00
cancel2
cond1
cond2
cond3
cond4	change 5M to 50000; add more printfs.	2007-01-20 19:21:18 +00:00
cond5	change count from 5M to 50000	2007-01-20 19:22:29 +00:00
cond6	Add tests for pthread_cond_timedwait() at time zero, as discussed	2004-12-29 20:34:11 +00:00
condcancel1
conddestroy1	Disable the conddestroy1 test. IEEE Std 1003.1, 2004 Edition says:	2007-01-20 19:40:06 +00:00
detach1	test pthread_detach.	2005-01-21 11:54:24 +00:00
exit1
find	add a test which exercises libpthread's ability to remember the	2009-04-02 12:58:44 +00:00
fork
fpu	No, it's not wrong after all. Sorry about the churn. I am going to adjust	2008-03-09 22:35:17 +00:00
kill1	Use sig_atomic_t	2006-03-20 00:22:38 +00:00
mutex1
mutex2
mutex3
mutex4
name
once1
once2
once3	Oops, don't include an extra bonus deadlock.	2005-07-16 23:12:02 +00:00
preempt1	The manual for open(2) says that -1 indicate a failure, not 0. And I	2006-04-12 14:01:52 +00:00
resolv	return NULL	2008-08-17 00:19:52 +00:00
rwlock1
sem	Copy sysconf(_SC_SEMAPHORES) test from regress/lib/librt/sem/sem.c	2006-04-18 12:21:05 +00:00
sem2
sigalarm	Block SIGALRM in the 'setup' thread, otherwise the alarm may not be taken	2007-09-09 01:08:56 +00:00
siglongjmp1
sigmask1
sigmask2	sig_atomic_t isn't necessarily compatible with the %d printf format,	2005-03-05 14:34:29 +00:00
sigmask3	Signal masks are thread private, and there is no guarantee of the order in	2006-12-26 20:29:03 +00:00
sigmask4	10 seconds is more than enough time to wait.	2005-07-27 00:02:14 +00:00
sigsuspend
sleep1	remove obsolete comment.	2009-03-08 19:17:11 +00:00
Makefile	add a test which exercises libpthread's ability to remember the	2009-04-02 12:58:44 +00:00