Modify or examine the signal-blocked mask of a thread
#include <sys/neutrino.h> int SignalProcmask( pid_t pid, int tid, int how, const sigset_t* set, sigset_t* oldset ); int SignalProcmask_r( pid_t pid, int tid, int how, const sigset_t* set, sigset_t* oldset );
- 0, or a process ID; see below.
- 0, or a thread ID; see below.
- The manner in which you want to change the set:
- SIG_BLOCK — the resulting set is the union of the current set and the signal set pointed to by set.
- SIG_UNBLOCK — the resulting set is the intersection of the current set and the signal set pointed to by set.
- SIG_SETMASK — the resulting set is the signal set pointed to by set.
As a special case, you can use the how argument to query the current set of pending signals:
- SIG_PENDING — the combined set of pending signals on the thread and process are saved in the signal set pointed to by oldset. The set argument is ignored.
- NULL, or a pointer to a sigset_t object that specified the set of signals to be used to change the currently blocked set.
NULL, or a pointer to a sigset_t object
where the function can store the previous blocked mask.
You can use various combinations of set and oldset to query or change (or both) the signal-blocked mask for a signal.
Use the -l c option to qcc to link against this library. This library is usually included automatically.
These kernel calls modify or examine the signal-blocked mask of the thread tid in process pid. If pid is zero, the current process is assumed. If tid is zero, pid is ignored and the calling thread is used.
The SignalProcmask() and SignalProcmask_r() functions are identical, except in the way they indicate errors. See the Returns section for details.
- Instead of using these kernel calls directly, consider calling pthread_sigmask() or sigprocmask() .
- In order to set the signal-blocked mask for a process with a different real or effective user ID, your process must have the PROCMGR_AID_SIGNAL ability enabled. For more information, see procmgr_ability() .
When a signal is unmasked, the kernel checks for pending signals on the thread and, if there aren't any pending, checks for pending signals on the process:
|Signal pending on thread||The signal is immediately acted upon.|
|Signal pending on process||The signal is moved to the thread and is immediately acted upon.|
|No signal pending||No signal action performed until delivery of an unblocked signal.|
It isn't possible to block the SIGCONT, SIGKILL, or SIGSTOP signals. It also isn't possible to unmask the special BlackBerry 10 OS signals (SIGSELECT and the unnamed ones).
When a signal handler is invoked, the signal responsible is automatically masked before its handler is called; see SignalAction() . If the handler returns normally, the operating system restores the signal mask present just before the handler was called as an atomic operation. Changes made using SignalProcmask() in the handler are undone.
When a signal is targeted at a process, the kernel delivers it to at most one thread (see SignalKill() ) that has the signal unblocked. If multiple threads have the signal unblocked, only one thread is given the signal. Which thread receives the signal isn't deterministic. To make it deterministic, you can:
- Have all threads except one block all signals; that thread
handles all signals.
- Target signals to specific threads.
If all threads have the signal blocked, it's made pending on the process. The first thread to unblock the signal receives the pending signal. If a signal is pending on a thread, it's never retargetted to the process or another thread, regardless of changes to the signal-blocked mask.
Signals targeted at a thread always affect that thread alone.
These calls don't block.
The only difference between these functions is the way they indicate errors:
- If an error occurs, -1 is returned and errno is set. Any other value returned indicates success.
- EOK is returned on success. This function does NOT set errno. If an error occurs, any value in the Errors section may be returned.
- The system was unable to allocate a signal handler. This indicates critically low memory.
- A fault occurred when the kernel tried to access the buffers provided.
- The value of how is invalid, or you tried to set SIGKILL or SIGSTOP to something other than SIG_DFL.
- The calling process doesn't have the required permission; see procmgr_ability() .
- The process indicated by pid or thread indicated by tid doesn't exist.
Last modified: 2013-12-23