freebsd-dev

History

Daniel Eischen 84001cde8f For now, build and install this as libkse instead of libpthread. This will avoid any accidental use of an experimental library. Suggested by: rwatson Approved by: re (jhb)		2002-12-08 22:43:31 +00:00
..
guard_b.c	Usage style sweep: spell "usage" with a small 'u'.	2002-04-22 13:44:47 +00:00
guard_b.exp	Implement pthread_attr_[gs]etguardsize(). Non-default-size stacks used to	2001-07-20 04:23:11 +00:00
guard_s.pl	Implement pthread_attr_[gs]etguardsize(). Non-default-size stacks used to	2001-07-20 04:23:11 +00:00
hello_b.c
hello_d.c
hello_d.exp
hello_s.c
join_leak_d.c	Add a test for PR 24345.	2001-05-20 23:12:13 +00:00
join_leak_d.exp	Add a test for PR 24345.	2001-05-20 23:12:13 +00:00
Makefile	For now, build and install this as libkse instead of libpthread.	2002-12-08 22:43:31 +00:00
mutex_d.c	Fix a couple of minor nits that prevented this from compiling.	2002-07-02 01:26:16 +00:00
mutex_d.exp
propagate_s.pl	Mechanically change all libc_r references to libpthread.	2002-09-16 19:29:34 +00:00
README	Mechanically change all libc_r references to libpthread.	2002-09-16 19:29:34 +00:00
sem_d.c
sem_d.exp
sigsuspend_d.c
sigsuspend_d.exp
sigwait_d.c
sigwait_d.exp
verify	Update the verify script.	2001-05-20 23:11:54 +00:00

README

$FreeBSD$

This test suite is meant to test general functionality of pthreads, as well as
provide a simple framework for regression tests.  In general, this test suite
can be used with any pthreads library, but in reality there are a number of
libpthread-specific aspects to this test suite which would require some
effort to get around if testing another pthreads library.

This test suite assumes that libpthread is installed.

There are two forms of test that the 'verify' script understands.  The simpler
form is the diff format, where the output of the test program is diff'ed with
the correspondingly named .exp file.  If there is diff output, the test fails.
The sequence test format is somewhat more complex, and is documented in the
command line usage output for verify.  The advantage of this format is that it
allows multiple tests to pass/fail within one program.

There is no driving need for test naming consistency, but the existing tests
generally follow these conventions:

<name>_d.c <name>_d.exp     : Diff mode C test and expected output file.
<name>_s.c                  : Sequence mode C test.
<name>_b*.c                 : Back end C program used by perl tests.
<name>_d.pl <name>_d.pl.exp : Diff mode perl test and expected output file.
<name>_s.pl                 : Sequence mode perl test.

<name> is something descriptive, such as "pr14685" in the case of a PR-related
regression test, or "mutex" in the case of a test of mutexes.