src-test2/lib/libpthread/thread/thr_spec.c, branch release/6.0.0_cvs FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F6.0.0_cvs 2005-11-03T00:35:26Z This commit was manufactured by cvs2svn to create tag 2005-11-03T00:35:26Z cvs2svn cvs2svn@FreeBSD.org 2005-11-03T00:35:26Z urn:sha1:3640cb54210edbb7edbf1b12ef0127ecfcea967d 'RELENG_6_0_0_RELEASE'. This commit was manufactured to restore the state of the 6.0-RELEASE image. Add code to support thread debugging. 2004-07-13T22:49:58Z David Xu davidxu@FreeBSD.org 2004-07-13T22:49:58Z urn:sha1:566382df0ad602942b46c4de0161beee34bb5098 1. Add global varible _libkse_debug, debugger uses the varible to identify libpthread. when the varible is written to non-zero by debugger, libpthread will take some special action at context switch time, it will check TMDF_DOTRUNUSER flags, if a thread has the flags set by debugger, it won't be scheduled, when a thread leaves KSE critical region, thread checks the flag, if it was set, the thread relinquish CPU. 2. Add pq_first_debug to select a thread allowd to run by debugger. 3. Some names prefixed with _thr are renamed to _thread prefix. which is allowed to run by debugger. Add back a loop for up to PTHREAD_DESTRUCTOR_ITERATIONS to 2003-08-20T02:34:14Z Daniel Eischen deischen@FreeBSD.org 2003-08-20T02:34:14Z urn:sha1:83e387752192fe92ad4c5e46398edaf810ff448a destroy thread-specific data. Display a warning when thread specific data remains after PTHREAD_DESTRUCTOR_ITERATIONS. Reviewed by: davidxu Access user provided pointer out of lock, and also check the case when 2003-08-16T05:19:00Z David Xu davidxu@FreeBSD.org 2003-08-16T05:19:00Z urn:sha1:61cc495a297c639149178e15b218175ddd285cf2 a key is less than 0. Revamp libpthread so that it has a chance of working in an SMP 2003-04-18T05:04:16Z Daniel Eischen deischen@FreeBSD.org 2003-04-18T05:04:16Z urn:sha1:a0240e2cb0b1ef8e5b61930ac2b850c884daaba8 environment. This includes support for multiple KSEs and KSEGs. The ability to create more than 1 KSE via pthread_setconcurrency() is in the works as well as support for PTHREAD_SCOPE_SYSTEM threads. Those should come shortly. There are still some known issues which davidxu and I are working on, but it'll make it easier for us by committing what we have. This library now passes all of the ACE tests that libc_r passes with the exception of one. It also seems to work OK with KDE including konqueror, kwrite, etc. I haven't been able to get mozilla to run due to lack of java plugin, so I'd be interested to see how it works with that. Reviewed by: davidxu Make the changes needed for libpthread to compile in its new home. 2002-09-16T08:45:36Z Jonathan Mini mini@FreeBSD.org 2002-09-16T08:45:36Z urn:sha1:cc118d869b950c0c5b934133ed4184e83d88553b The new libpthread will provide POSIX threading support using KSE. These files were previously repo-copied from src/lib/libc_r. Reviewed by: deischen Approved by: -arch Add the ability to recognize old references to keys, and return NULL 2002-03-19T22:58:56Z Daniel Eischen deischen@FreeBSD.org 2002-03-19T22:58:56Z urn:sha1:3003bdb5983ac249a54696112d841e1d6ed28d00 when old keys are referenced (after pthread_key_delete()) via pthread_getspecific(). To be consistent, use the __weak_reference macro from <sys/cdefs.h> 2001-04-10T04:19:21Z Daniel Eischen deischen@FreeBSD.org 2001-04-10T04:19:21Z urn:sha1:437df4859af22264a2c620a3720c776bf0c4a58d instead of #pragma weak to create weak definitions. Suggested by: bde Add weak definitions for wrapped system calls. In general: 2001-01-24T13:03:38Z Daniel Eischen deischen@FreeBSD.org 2001-01-24T13:03:38Z urn:sha1:e5106342c6de9cbe26c4827e4e29bae309cd8cfb _foo - wrapped system call foo - weak definition to _foo and for cancellation points: _foo - wrapped system call __foo - enter cancellation point, call _foo(), leave cancellation point foo - weak definition to __foo Change use of global _thread_run to call a function to get the currently running thread. Make all pthread_foo functions weak definitions to _pthread_foo, where _pthread_foo is the implementation. This allows an application to provide its own pthread functions. Provide slightly different versions of pthread_mutex_lock and pthread_mutex_init so that we can tell the difference between a libc mutex and an application mutex. Threads holding mutexes internal to libc should never be allowed to exit, call signal handlers, or cancel. Approved by: -arch -Wall and minor style(9) cleanups. 1999-12-28T18:13:04Z Daniel Eischen deischen@FreeBSD.org 1999-12-28T18:13:04Z urn:sha1:1752e66d49ea5d9653b0cec4df9949774de0b806