+2005-05-30 Jakub Jelinek <jakub@redhat.com>
+
+ * man/Makefile (SOURCES): Remove all man pages but
+ pthread_cleanup_push.man, pthread_kill_other_threads_np.man
+ and pthread_mutexattr_setkind_np.man.
+ * man/pthread_cleanup_push.man: Replace (3) with (3p) where man page
+ was not kept.
+ * man/pthread_kill_other_threads_np.man: Likewise.
+ * man/pthread_mutexattr_setkind_np.man: Likewise.
+
2005-05-23 Roland McGrath <roland@redhat.com>
* sysdeps/arm, sysdeps/unix/sysv/linux/arm: Subdirectories moved to
-SOURCES=pthread_atfork.man pthread_attr_init.man pthread_cancel.man \
- pthread_cleanup_push.man pthread_cond_init.man \
- pthread_condattr_init.man pthread_create.man pthread_detach.man \
- pthread_equal.man pthread_exit.man pthread_join.man \
- pthread_key_create.man pthread_mutex_init.man \
- pthread_mutexattr_init.man pthread_once.man pthread_self.man \
- pthread_setschedparam.man pthread_sigmask.man sem_init.man \
+SOURCES= pthread_cleanup_push.man \
pthread_kill_other_threads_np.man pthread_mutexattr_setkind_np.man
MANPAGES=$(SOURCES:.man=.3thr)
.SH DESCRIPTION
Cleanup handlers are functions that get called when a thread
-terminates, either by calling !pthread_exit!(3) or because of
+terminates, either by calling !pthread_exit!(3p) or because of
cancellation. Cleanup handlers are installed and removed following a
stack-like discipline.
!pthread_cleanup_push! installs the |routine| function with argument
|arg| as a cleanup handler. From this point on to the matching
!pthread_cleanup_pop!, the function |routine| will be called with
-arguments |arg| when the thread terminates, either through !pthread_exit!(3)
+arguments |arg| when the thread terminates, either through !pthread_exit!(3p)
or by cancellation. If several cleanup handlers are active at that
point, they are called in LIFO order: the most recently installed
handler is called first.
of the matching !pthread_cleanup_pop!.
!pthread_cleanup_push_defer_np! is a non-portable extension that
-combines !pthread_cleanup_push! and !pthread_setcanceltype!(3).
+combines !pthread_cleanup_push! and !pthread_setcanceltype!(3p).
It pushes a cleanup handler just as !pthread_cleanup_push! does, but
also saves the current cancellation type and sets it to deferred
cancellation. This ensures that the cleanup mechanism is effective
Xavier Leroy <Xavier.Leroy@inria.fr>
.SH "SEE ALSO"
-!pthread_exit!(3),
-!pthread_cancel!(3),
-!pthread_setcanceltype!(3).
+!pthread_exit!(3p),
+!pthread_cancel!(3p),
+!pthread_setcanceltype!(3p).
.SH EXAMPLE
.fi
Notice that the code above is safe only in deferred cancellation mode
-(see !pthread_setcanceltype!(3)). In asynchronous cancellation mode,
+(see !pthread_setcanceltype!(3p)). In asynchronous cancellation mode,
a cancellation can occur between !pthread_cleanup_push! and
!pthread_mutex_lock!, or between !pthread_mutex_unlock! and
!pthread_cleanup_pop!, resulting in both cases in the thread trying to
e.g. !execve!(2).
Termination of the other threads is not performed through
-!pthread_cancel!(3) and completely bypasses the cancellation
+!pthread_cancel!(3p) and completely bypasses the cancellation
mechanism. Hence, the current settings for cancellation state and
cancellation type are ignored, and the cleanup handlers are not
executed in the terminated threads.
.SH "SEE ALSO"
!execve!(2),
-!pthread_setcancelstate!(3),
-!pthread_setcanceltype!(3),
-!pthread_cancel!(3).
+!pthread_setcancelstate!(3p),
+!pthread_setcanceltype!(3p),
+!pthread_cancel!(3p).
.SH BUGS
.SH DESCRIPTION
-These functions are deprecated, use !pthread_mutexattr_settype!(3)
-and !pthread_mutexattr_gettype!(3) instead.
+These functions are deprecated, use !pthread_mutexattr_settype!(3p)
+and !pthread_mutexattr_gettype!(3p) instead.
.SH "RETURN VALUE"
!pthread_mutexattr_getkind_np! always returns 0.
Xavier Leroy <Xavier.Leroy@inria.fr>
.SH "SEE ALSO"
-!pthread_mutexattr_settype!(3),
-!pthread_mutexattr_gettype!(3).
+!pthread_mutexattr_settype!(3p),
+!pthread_mutexattr_gettype!(3p).