2 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved.
3 .\" Copyright (c) 2001, the Institute of Electrical and Electronics Engineers, Inc. and The Open Group. All Rights Reserved.
4 .\" Portions Copyright (c) 1995 IEEE. All Rights Reserved
5 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at
6 .\" http://www.opengroup.org/bookstore/.
7 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
8 .\" This notice shall appear on any product containing this material.
9 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
10 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
11 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
12 .TH PTHREAD_SIGMASK 3C "Mar 23, 2005"
14 pthread_sigmask \- change or examine calling thread's signal mask
18 cc -mt [ \fIflag\fR... ] \fIfile\fR... -lpthread [ \fIlibrary\fR... ]
22 \fBint\fR \fBpthread_sigmask\fR(\fBint\fR \fIhow\fR, \fBconst sigset_t *\fR\fIset\fR, \fBsigset_t *\fR\fIoset\fR);
28 The \fBpthread_sigmask()\fR function changes or examines a calling thread's
29 signal mask. Each thread has its own signal mask. A new thread inherits the
30 calling thread's signal mask and priority; however, pending signals are not
31 inherited. Signals pending for a new thread will be empty.
34 If the value of the argument \fIset\fR is not \fINULL\fR, \fIset\fR points to a
35 set of signals that can modify the currently blocked set. If the value of
36 \fIset\fR is \fINULL\fR, the value of \fIhow\fR is insignificant and the
37 thread's signal mask is unmodified; thus, \fBpthread_sigmask()\fR can be used
38 to inquire about the currently blocked signals.
41 The value of the argument \fIhow\fR specifies the method in which the set is
42 changed and takes one of the following values:
49 \fIset\fR corresponds to a set of signals to block. They are added to the
56 \fB\fBSIG_UNBLOCK\fR\fR
59 \fIset\fR corresponds to a set of signals to unblock. These signals are deleted
60 from the current signal mask.
66 \fB\fBSIG_SETMASK\fR\fR
69 \fIset\fR corresponds to the new signal mask. The current signal mask is
70 replaced by \fBset\fR.
75 If the value of \fIoset\fR is not \fINULL\fR, it points to the location where
76 the previous signal mask is stored.
80 Upon successful completion, the \fBpthread_sigmask()\fR function returns
81 \fB0\fR. Otherwise, it returns a non-zero value.
85 The \fBpthread_sigmask()\fR function will fail if:
92 The value of \fIhow\fR is not defined and \fIoset\fR is \fINULL\fR.
97 \fBExample 1 \fRCreate a default thread that can serve as a signal
98 catcher/handler with its own signal mask.
101 The following example shows how to create a default thread that can serve as a
102 signal catcher/handler with its own signal mask. \fBnew\fR will have a
103 different value from the creator's signal mask.
107 As POSIX threads and Solaris threads are fully compatible even within the same
108 process, this example uses \fBpthread_create\fR(3C) if you execute \fBa.out
109 0\fR, or \fBthr_create\fR(3C) if you execute \fBa.out 1\fR.
119 The \fBsigemptyset\fR(3C) function initializes a null signal set, \fBnew\fR.
120 The \fBsigaddset\fR(3C) function packs the signal, \fBSIGINT\fR, into that new
127 Either \fBpthread_sigmask()\fR or \fBthr_sigsetmask()\fR is used to mask the
128 signal, \fBSIGINT\fR (CTRL-C), from the calling thread, which is \fBmain()\fR.
129 The signal is masked to guarantee that only the new thread will receive this
136 \fBpthread_create()\fR or \fBthr_create()\fR creates the signal-handling
143 Using \fBpthread_join\fR(3C) or \fBthr_join\fR(3C), \fBmain()\fR then waits for
144 the termination of that signal-handling thread, whose \fBID\fR number is
145 \fBuser_threadID\fR; \fBmain()\fR will then \fBsleep\fR(3C) for 2 seconds,
146 after which the program terminates.
152 The signal-handling thread, \fBhandler\fR:
157 Assigns the handler \fBinterrupt()\fR to handle the signal \fBSIGINT\fR, by the
158 call to \fBsigaction\fR(2).
164 Resets its own signal set to \fInot block\fR the signal, \fBSIGINT\fR.
170 Sleeps for 8 seconds to allow time for the user to deliver the signal,
171 \fBSIGINT\fR, by pressing the \fBCTRL-C\fR.
180 thread_t user_threadID;
182 void *handler(\|), interrupt(\|);
185 main( int argc, char *argv[\|] ) {
189 sigaddset(&new, SIGINT);
192 case '0': /* POSIX */
193 pthread_sigmask(SIG_BLOCK, &new, NULL);
194 pthread_create(&user_threadID, NULL, handler,
196 pthread_join(user_threadID, NULL);
199 case '1': /* Solaris */
200 thr_sigsetmask(SIG_BLOCK, &new, NULL);
201 thr_create(NULL, 0, handler, argv[1], 0,
203 thr_join(user_threadID, NULL, NULL);
207 printf("thread handler, # %d, has exited\en",user_threadID);
209 printf("main thread, # %d is done\en", thr_self(\|));
213 struct sigaction act;
218 act.sa_handler = interrupt;
219 sigaction(SIGINT, &act, NULL);
221 case '0': /* POSIX */
222 pthread_sigmask(SIG_UNBLOCK, &new, NULL);
224 case '1': /* Solaris */
225 thr_sigsetmask(SIG_UNBLOCK, &new, NULL);
228 printf("\en Press CTRL-C to deliver SIGINT signal to the
230 sleep(8); /* give user time to hit CTRL-C */
237 printf("thread %d caught signal %d\en", thr_self(\|), sig);
240 void test_argv(char argv1[\|]) {
242 printf("use 0 as arg1 to use thr_create(\|);\en \e
243 or use 1 as arg1 to use pthread_create(\|)\en");
252 In the last example, the \fBhandler\fR thread served as a signal-handler while
253 also taking care of activity of its own (in this case, sleeping, although it
254 could have been some other activity). A thread could be completely dedicated to
255 signal-handling simply by waiting for the delivery of a selected signal by
256 blocking with \fBsigwait\fR(2). The two subroutines in the previous example,
257 \fBhandler()\fR and \fBinterrupt()\fR, could have been replaced with the
264 handler(void *unused)
267 printf("thread %d is waiting for you to press the CTRL-C keys\en",
269 sigwait(&new, &signal);
270 printf("thread %d has received the signal %d \en", thr_self(\|),
274 /* pthread_create(\|) and thr_create(\|) would use NULL instead
275 of argv[1] for the arg passed to handler(\|) */
281 In this routine, one thread is dedicated to catching and handling the signal
282 specified by the set \fBnew\fR, which allows \fBmain()\fR and all of its other
283 sub-threads, created \fIafter\fR \fBpthread_sigmask()\fR or
284 \fBthr_sigsetmask()\fR masked that signal, to continue uninterrupted. Any use
285 of \fBsigwait\fR(2) should be such that all threads block the signals passed
286 to \fBsigwait\fR(2) at all times. Only the thread that calls \fBsigwait()\fR
287 will get the signals. The call to \fBsigwait\fR(2) takes two arguments.
291 For this type of background dedicated signal-handling routine, a Solaris daemon
292 thread can be used by passing the argument \fBTHR_DAEMON\fR to
293 \fBthr_create\fR(3C).
298 See \fBattributes\fR(5) for descriptions of the following attributes:
306 ATTRIBUTE TYPE ATTRIBUTE VALUE
308 Interface Stability Standard
310 MT-Level MT-Safe and Async-Signal-Safe
316 \fBsigaction\fR(2), \fBsigprocmask\fR(2), \fBsigwait\fR(2),
317 \fBcond_wait\fR(3C), \fBpthread_cancel\fR(3C), \fBpthread_create\fR(3C),
318 \fBpthread_join\fR(3C), \fBpthread_self\fR(3C), \fBsigaddset\fR(3C),
319 \fBsigemptyset\fR(3C), \fBsigsetops\fR(3C), \fBsleep\fR(3C),
320 \fBattributes\fR(5), \fBcancellation\fR(5), \fBstandards\fR(5)
324 It is not possible to block signals that cannot be caught or ignored (see
325 \fBsigaction\fR(2)). It is also not possible to block or unblock
326 \fBSIGCANCEL\fR, as \fBSIGCANCEL\fR is reserved for the implementation of POSIX
327 thread cancellation (see \fBpthread_cancel\fR(3C) and \fBcancellation\fR(5)).
328 This restriction is quietly enforced by the standard C library.
331 Using \fBsigwait\fR(2) in a dedicated thread allows asynchronously generated
332 signals to be managed synchronously; however, \fBsigwait\fR(2) should never be
333 used to manage synchronously generated signals.
336 Synchronously generated signals are exceptions that are generated by a thread
337 and are directed at the thread causing the exception. Since \fBsigwait()\fR
338 blocks waiting for signals, the blocking thread cannot receive a synchronously
342 The \fBsigprocmask\fR(2) function behaves the same as if
343 \fBpthread_sigmask()\fR has been called. POSIX leaves the semantics of the call
344 to \fBsigprocmask\fR(2) unspecified in a multi-threaded process, so programs
345 that care about POSIX portability should not depend on this semantic.
348 If a signal is delivered while a thread is waiting on a condition variable, the
349 \fBcond_wait\fR(3C) function will be interrupted and the handler will be
350 executed. The state of the lock protecting the condition variable is undefined
351 while the thread is executing the signal handler.
354 Although \fBpthread_sigmask()\fR is Async-Signal-Safe with respect to the
355 Solaris environment, this safeness is not guaranteed to be portable to other
359 Signals that are generated synchronously should not be masked. If such a signal
360 is blocked and delivered, the receiving process is killed.