summaryrefslogtreecommitdiffstats
path: root/man3/pthread_setcancelstate.3
diff options
context:
space:
mode:
Diffstat (limited to 'man3/pthread_setcancelstate.3')
-rw-r--r--man3/pthread_setcancelstate.322
1 files changed, 11 insertions, 11 deletions
diff --git a/man3/pthread_setcancelstate.3 b/man3/pthread_setcancelstate.3
index 287907657..62811ffdf 100644
--- a/man3/pthread_setcancelstate.3
+++ b/man3/pthread_setcancelstate.3
@@ -58,7 +58,7 @@ argument must have one of the following values:
.B PTHREAD_CANCEL_DEFERRED
A cancelation request is deferred until the thread next calls
a function that is a cancelation point (see
-.BR pthreads (7)).
+.MR pthreads 7 ).
This is the default cancelability type in all new threads,
including the initial thread.
.IP
@@ -97,7 +97,7 @@ Invalid value for
.IR type .
.SH ATTRIBUTES
For an explanation of the terms used in this section, see
-.BR attributes (7).
+.MR attributes 7 .
.TS
allbox;
lbx lb lb
@@ -131,7 +131,7 @@ glibc 2.0
POSIX.1-2001.
.SH NOTES
For details of what happens when a thread is canceled, see
-.BR \%pthread_cancel (3).
+.MR pthread_cancel 3 .
.P
Briefly disabling cancelability is useful
if a thread performs some critical action
@@ -146,7 +146,7 @@ is rarely useful.
Since the thread could be canceled at
.I any
time, it cannot safely reserve resources (e.g., allocating memory with
-.BR malloc (3)),
+.MR malloc 3 ),
acquire mutexes, semaphores, or locks, and so on.
Reserving resources is unsafe because the application has no way of
knowing what the state of these resources is when the thread is canceled;
@@ -154,7 +154,7 @@ that is, did cancelation occur before the resources were reserved,
while they were reserved, or after they were released?
Furthermore, some internal data structures
(e.g., the linked list of free blocks managed by the
-.BR malloc (3)
+.MR malloc 3
family of functions) may be left in an inconsistent state
if cancelation occurs in the middle of the function call.
Consequently, clean-up handlers cease to be useful.
@@ -162,7 +162,7 @@ Consequently, clean-up handlers cease to be useful.
Functions that can be safely asynchronously canceled are called
.IR "async-cancel-safe functions" .
POSIX.1-2001 and POSIX.1-2008 require only that
-.BR pthread_cancel (3),
+.MR pthread_cancel 3 ,
.BR pthread_setcancelstate (),
and
.BR pthread_setcanceltype ()
@@ -192,9 +192,9 @@ argument of
.BR pthread_setcanceltype ().
.SH EXAMPLES
See
-.BR pthread_cancel (3).
+.MR pthread_cancel 3 .
.SH SEE ALSO
-.BR pthread_cancel (3),
-.BR pthread_cleanup_push (3),
-.BR pthread_testcancel (3),
-.BR pthreads (7)
+.MR pthread_cancel 3 ,
+.MR pthread_cleanup_push 3 ,
+.MR pthread_testcancel 3 ,
+.MR pthreads 7