32f6962a6f
Only catch SIGINFO (for dumping thread states) when LIBPTHREAD_DEBUG
is defined in the environment.
Modify the code path of the ifdef NOTYET part of _kse_single_thread():
o Don't reinitialise the atfork() handler list in the child. We
are meant to call the child handler, and on subsequent fork()s
should call all three functions as normal.
o Don't reinitialise the thread specific keyed data in the
child after a fork. Applications may require this for context.
o Reinitialise curthread->tlflags after removing ourselves from
(and reinitialising) the various internal thread lists.
o Reinitialise __malloc_lock in the child after fork() (to balance
our explicitly taking the lock prior to the fork()).
With these changes, it is possible to enable the NOTYET code in
thr_kern.c to allow the use of non-async-safe functions after
fork()ing from a threaded program.
Eliminate a race condition in timed waits (cv, mutex, and sleeps).
Don't forget to initialize a tailq before using it.
For the ``#ifdef NOTYET'' code that allows calling non-async-safe
functions in the child after a fork() from a threaded process,
use __sys_setprocmask() rather than setprocmask() to keep our
signal handling sane. Without this fix, signals are essentially
ignored in said child and things such as protection violations
result in an endless busy loop.
Allocate a thread's tcb last so it is easier to handle failures to
malloc() siginfo.
Include needed headers that were obtained through <pthread.h>. Sort headers
while here.
amd64
-----
Fix a race condition introduced when redzones were added. Use an
atomic operation to return and adjust the stack (amd64).
test
-----
o Include <string.h>
o Make this ILP32/LP64 clean: cast pointers to long.
Approved by: re (scottl)
$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.