Search all pages
Professions, Sciences, Humanities, Business, ...
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Conversions, tests, processing, manipulation,...
Integer, Floating point, Matrix, Statistics, Boolean, ...
Algorithms, Memory, Process control, Debugging, ...
Data storage, Integrity, Encryption, Compression, ...
Networks, protocols, Interprocess, Remote, Client Server, ...
Timing, Calendar and Clock, Audio, Video, Printer, Controls...
Management, Filtering, File & Directory access, Viewers, ...
RocketLink!--> Man page versions:
PTHREAD_TESTCANCEL(3) OpenBSD Programmer's Manual PTHREAD_TESTCANCEL(3)
pthread_setcancelstate, pthread_setcanceltype, pthread_testcancel - set
pthread_setcancelstate(int state, int *oldstate);
pthread_setcanceltype(int type, int *oldtype);
The pthread_setcancelstate() function atomically both sets the calling
thread's cancelability state to the indicated state and returns the pre-
vious cancelability state at the location referenced by oldstate. Legal
values for state are PTHREAD_CANCEL_ENABLE and PTHREAD_CANCEL_DISABLE.
The pthread_setcanceltype() function atomically both sets the calling
thread's cancelability type to the indicated type and returns the previ-
ous cancelability type at the location referenced by oldtype. Legal val-
ues for type are PTHREAD_CANCEL_DEFERRED and PTHREAD_CANCEL_ASYNCHRONOUS.
The cancelability state and type of any newly created threads, including
the thread in which main() was first invoked, are PTHREAD_CANCEL_ENABLE
and PTHREAD_CANCEL_DEFERRED respectively.
The pthread_testcancel() function creates a cancellation point in the
calling thread. The pthread_testcancel() function has no effect if cance-
lability is disabled.
The cancelability state of a thread determines the action taken upon re-
ceipt of a cancellation request. The thread may control cancellation in a
number of ways.
Each thread maintains its own ``cancelability state'' which may be encod-
ed in two bits:
Cancelability Enable When cancelability is PTHREAD_CANCEL_DISABLE, can-
cellation requests against the target thread are held pending.
Cancelability Type When cancelability is enabled and the cancelability
type is PTHREAD_CANCEL_ASYNCHRONOUS, new or pending cancellation
requests may be acted upon at any time. When cancelability is
enabled and the cancelability type is PTHREAD_CANCEL_DEFERRED,
cancellation requests are held pending until a cancellation point
(see below) is reached. If cancelability is disabled, the setting
of the cancelability type has no immediate effect as all cancel-
lation requests are held pending; however, once cancelability is
enabled again the new type will be in effect.
Cancellation points will occur when a thread is executing the following
functions: close(), creat(), fcntl(), fsync(), msync(), nanosleep(),
open(), pause(), pthread_cond_timedwait(), pthread_cond_wait(),
pthread_join(), pthread_testcancel(), read(), sigwaitinfo(),
sigsuspend(), sigwait(), sleep(), system(), tcdrain(), wait(), waitpid(),
If successful, the pthread_setcancelstate() and pthread_setcanceltype()
functions will return zero. Otherwise, an error number shall be returned
to indicate the error.
The pthread_setcancelstate() and pthread_setcanceltype() functions are
used to control the points at which a thread may be asynchronously can-
celed. For cancellation control to be usable in modular fashion, some
rules must be followed.
For purposes of this discussion, consider an object to be a generaliza-
tion of a procedure. It is a set of procedures and global variables writ-
ten as a unit and called by clients not known by the object. Objects may
depend on other objects.
First, cancelability should only be disabled on entry to an object, never
explicitly enabled. On exit from an object, the cancelability state
should always be restored to its value on entry to the object.
This follows from a modularity argument: if the client of an object (or
the client of an object that uses that object) has disabled cancelabili-
ty, it is because the client doesn't want to have to worry about how to
clean up if the thread is canceled while executing some sequence of ac-
tions. If an object is called in such a state and it enables cancelabili-
ty and a cancellation request is pending for that thread, then the thread
will be canceled, contrary to the wish of the client that disabled.
Second, the cancelability type may be explicitly set to either deferred
or asynchronous upon entry to an object. But as with the cancelability
state, on exit from an object that cancelability type should always be
restored to its value on entry to the object.
Finally, only functions that are cancel-safe may be called from a thread
that is asynchronously cancelable.
The function pthread_setcancelstate() may fail with:
[EINVAL] The specified state is not PTHREAD_CANCEL_ENABLE or
The function pthread_setcanceltype() may fail with:
[EINVAL] The specified state is not PTHREAD_CANCEL_DEFERRED or
pthread_testcancel() conforms to ISO/IEC 9945-1 ANSI/IEEE (``POSIX'') Std
1003.1 Second Edition 1996-07-12.
OpenBSD 2.6 January 17, 1999 2
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.
(Corrections, notes, and links courtesy of RocketAware.com)
RocketLink!--> Man page versions:
Search | About | Comments | Submit Path: RocketAware > man pages >
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments