diff options
author | Mystery Man <unknown@mandriva.org> | 2001-05-14 14:17:54 +0000 |
---|---|---|
committer | Mystery Man <unknown@mandriva.org> | 2001-05-14 14:17:54 +0000 |
commit | 16984701aa5165b77f229cc318e8025ee8cf81b5 (patch) | |
tree | 923ed2780582f751b2be106641be35cf71fedd66 /mdk-stage1/dietlibc/libpthread/README | |
parent | c5050eb3ba91cf0eab748b773dcbb34b88ae88bc (diff) | |
download | drakx-backup-do-not-use-16984701aa5165b77f229cc318e8025ee8cf81b5.tar drakx-backup-do-not-use-16984701aa5165b77f229cc318e8025ee8cf81b5.tar.gz drakx-backup-do-not-use-16984701aa5165b77f229cc318e8025ee8cf81b5.tar.bz2 drakx-backup-do-not-use-16984701aa5165b77f229cc318e8025ee8cf81b5.tar.xz drakx-backup-do-not-use-16984701aa5165b77f229cc318e8025ee8cf81b5.zip |
This commit was manufactured by cvs2svn to create branch 'dietlibc'.topic/dietlibc
Diffstat (limited to 'mdk-stage1/dietlibc/libpthread/README')
-rw-r--r-- | mdk-stage1/dietlibc/libpthread/README | 42 |
1 files changed, 42 insertions, 0 deletions
diff --git a/mdk-stage1/dietlibc/libpthread/README b/mdk-stage1/dietlibc/libpthread/README new file mode 100644 index 000000000..3139c731d --- /dev/null +++ b/mdk-stage1/dietlibc/libpthread/README @@ -0,0 +1,42 @@ +LIBPTHREAD + + This is the pthread implementation of dietlibc. + Written from scratch by Olaf Dreesen. + +1. STATUS: incomplete but should work (or not... I had a lot of heisen-bugs...) + On non i386 archs the kernel header have major differences... + NO workaround yet for this problems... + +It's like linuxthreads a clone base thread implementation. + +I have implemented a "Manager Thread" with all the pain it involves... +Nested thread creation is now working fine... + + +2. HOW-TO make this lib: + + 1. generate the dietlibc in the parent directory. + and make sure you have WANT_THREAD_SAVE active in the file: + dietfeatures.h + + 2. change back here and type make + + and then you should have a libpthread.a + + +3. NOTES + +NON STANDARD SIGNAL HANDLING for the threads: + + SIGHUP the targeted thread is canceled + depends on the cancel type of the thread. + + ASYNCHRONOUS: the signal handler will KILL the thread immediately. + + DEFERRED: the signal handler mark its thread as canceled. + (only for the sig-handler to do some sane stuff...) + + SIGTERM the thread is KILLED + if the thread signaled is the main thread, then ALL child-threads + will get a SIGHUP and after some micros a SIGTERM.... + |