SignalAction(), SignalAction_r()

Examine and/or specify actions for signals

Synopsis:

#include <sys/neutrino.h>

int SignalAction( pid_t pid,
                  void ( * sigstub)(),
                  int signo,
                  const struct sigaction * act,
                  struct sigaction * oact );

int SignalAction_r( pid_t pid,
                    void * (sigstub)(),
                    int signo,
                    const struct sigaction * act,
                    struct sigaction * oact );

Since:

BlackBerry 10.0.0

Arguments:

pid
A process ID, or 0 for the current process.
sigstub
The address of a signal stub handler. This is a small piece of code in the user's space that interfaces the user's signal handler to the kernel. The library provides a standard one, __signalstub(). This argument can be NULL if act is also NULL.
signo
The signal whose action you want to set or get; see " POSIX signals," below.
act
NULL, or a pointer to a sigaction structure that specifies the new action for the signal. For more information, see " Signal actions," below.
oact
NULL, or a pointer to a sigaction structure where the function can store the old action.

Library:

libc

Use the -l c option to qcc to link against this library. This library is usually included automatically.

Description:

The SignalAction() and SignalAction_r() kernel calls let the calling process examine or specify (or both) the action to be associated with a specific signal in the process pid. If pid is zero, the calling process is used. The argument signo specifies the signal.

  • You should call the POSIX sigaction() function or the ANSI signal() function instead of using these kernel calls directly.
  • In order to attach signal handlers to 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().

These functions are identical except in the way they indicate errors. See the Returns section for details.

POSIX signals

The signals are defined in <signal.h>, and so are these global variables:

char * const sys_siglist[]
An array of signal names.
int sys_nsig
The number of entries in the sys_siglist array.

As mentioned earlier, the OS defines a total of 64 signals. Their range is as follows:

Signal range Description
1 ... 57 57 POSIX signals (including traditional UNIX signals)
41 ... 56 16 POSIX realtime signals (SIGRTMIN to SIGRTMAX)
57 ... 64 Eight special-purpose BlackBerry 10 OS signals

The POSIX and UNIX signals include:

SIGHUP
Hangup.
SIGINT
Interrupt.
SIGQUIT
Quit.
SIGILL
Illegal instruction (not reset when caught).

One possible cause for this signal is trying to perform an operation that requires I/O privileges. A thread can request these privileges by making sure it has the PROCMGR_AID_IO ability enabled (see procmgr_ability()) and then calling ThreadCtl(), specifying the _NTO_TCTL_IO flag:

ThreadCtl( _NTO_TCTL_IO, 0 );
  
SIGTRAP
Trace trap (not reset when caught).
SIGIOT
IOT instruction.
SIGABRT
Used by abort().
SIGDEADLK
Mutex deadlock; see SyncMutexEvent().

SIGDEADLK and SIGEMT use the same signal number.

SIGEMT
EMT instruction (emulation trap).
SIGFPE
Floating point exception.
SIGKILL
Kill (can't be caught or ignored)
SIGBUS
Bus error.
SIGSEGV
Segmentation violation.
SIGSYS
Bad argument to system call.
SIGPIPE
Write on pipe with no reader.
SIGALRM
Realtime alarm clock.
SIGTERM
Software termination signal from kill.
SIGUSR1
User-defined signal 1.
SIGUSR2
User-defined signal 2.
SIGCHLD
Death of child.
SIGPWR
Power-fail restart.
SIGWINCH
Window change.
SIGURG
Urgent condition on I/O channel.
SIGPOLL
System V name for SIGIO.
SIGIO
Asynchronous I/O.
SIGSTOP
Sendable stop signal not from tty.
SIGTSTP
Stop signal from tty.
SIGCONT
Make a stopped process continue.
SIGTTIN
Attempted background tty read.
SIGTTOU
Attempted background tty write.

You can't ignore or catch SIGCONT, SIGKILL, or SIGSTOP.

There are 16 POSIX 1003.1b realtime signals, including:

SIGRTMIN
First realtime signal.
SIGRTMAX
Last realtime signal.

The entire range of signals goes from _SIGMIN (1) to _SIGMAX (64).

BlackBerry 10 OS signals

BlackBerry 10 OS uses the top eight signals for special purposes. They're always masked, and attempts to unmask them are ignored. They include named signals (e.g., SIGSELECT) and unnamed ones.

Signal actions

If act isn't NULL, then the specified signal is modified. If oact isn't NULL, the previous action is stored in the structure it points to. You can use various combinations of act and oact to query or set (or both) the action for a signal.

The structure sigaction contains the following members:

void (*sa_handler)();
The address of a signal handler or action for nonqueued signals.
void (*sa_sigaction) (int signo, siginfo_t *info, void *other);
The address of a signal handler or action for queued signals.
sigset_t sa_mask
An additional set of signals to be masked (blocked) during execution of the signal-catching function.
int sa_flags
Special flags that affect the behavior of the signal:
  • SA_NOCLDSTOP — don't generate a SIGCHLD on the parent for children who stop via SIGSTOP. This flag is used only when the signal is SIGCHLD.
  • SA_SIGINFO — queue this signal. The default is not to queue a signal delivered to a process. If a signal isn't queued, and the same signal is set multiple times on a process or thread before it runs, only the last signal is delivered. If you set the SA_SIGINFO flag, the signals are queued, and they're all delivered.

The sa_handler and sa_sigaction members of act are implemented as a union, and share common storage. They differ only in their prototype, with sa_handler being used for POSIX 1003.1a signals, and sa_sigaction being used for POSIX 1003.1b queued realtime signals. The values stored using either name can be one of:

function
The address of a signal-catching function. See below for details.
SIG_DFL
Use the default action for the signal:
  • SIGIO, SIGURG, and SIGWINCH — ignore the signal.
  • SIGCHLD — ignore the signal, but still let the process's children become zombies.
  • SIGSTOP, SIGTSTP, SIGTTIN, and SIGTTOU — stop the process.
  • SIGCONT — make the program continue.
  • all other signals — kill the process.
SIG_IGN
Ignore the signal. Setting SIG_IGN for a signal that's pending discards all pending signals, whether it's blocked or not. New signals are discarded. If you set the action for SIGCHLD to SIG_IGN, your process's children won't enter the zombie state, and the process won't be able to use wait() or waitpid() to wait on their deaths.

The function member of sa_handler or sa_sigaction is always invoked with the following arguments:

void handler(int signo, siginfo_t* info, void* other)

If you have an old-style signal handler of the form:

void handler(int signo)

the microkernel passes the extra arguments, but the function simply ignores them.

While in the handler, signo is masked, preventing nested signals of the same type. In addition, any signals set in the sa_mask member of act are also ORed into the mask. When the handler returns through a normal return, the previous mask is restored, and any pending and now unmasked signals are acted on. You return to the point in the program where it was interrupted. If the thread was blocked in the kernel when the interruption occurred, the kernel call returns with an EINTR (see ChannelCreate() and SyncMutexLock() for exceptions to this).

It isn't safe to use floating-point operations in signal handlers.

When you specify a handler, you must provide the address of a signal stub handler for sigstub. This is a small piece of code in the user's space that interfaces the user's signal handler to the kernel. The library provides a standard one, __signalstub().

The siginfo_t structure of the function in sa_handler or sa_sigaction contains at least the following members:

int si_signo
The signal number, which should match the signo argument to the handler.
int si_code
A signal code, provided by the generator of the signal:
  • SI_USER — the kill() function generated the signal.
  • SI_QUEUE — the sigqueue() function generated the signal.
  • SI_TIMER — a timer generated the signal.
  • SI_ASYNCIO — asynchronous I/O generated the signal.
  • SI_MESGQ — POSIX (not BlackBerry 10 OS) messages queues generated the signal.
union sigval si_value
A value associated with the signal, provided by the generator of the signal.

Signal handlers and actions are defined for the process and affect all threads in the process. For example, if one thread ignores a signal, then all threads ignore the signal.

You can target a signal at a thread, process or process group (see SignalKill()). When targeted at a process, at most one thread receives the signal. This thread must have the signal unblocked (see SignalProcmask()) to be a candidate for receiving it. All synchronously generated signals (e.g. SIGSEGV) are always delivered to the thread that caused them.

In a multithreaded process, if a signal terminates a thread, by default all threads and thus the process are terminated. You can override this standard POSIX behavior when you create the thread; see ThreadCreate().

If you use longjmp() to return from a signal handler, the signal remains masked. You can use siglongjmp() to restore the mask to the state saved by a previous call to sigsetjmp().

Blocking states

These calls don't block.

Returns:

The only difference between these functions is the way they indicate errors:

SignalAction()
If an error occurs, -1 is returned and errno is set. Any other value returned indicates success.
SignalAction_r()
EOK is returned on success. This function does NOT set errno. If an error occurs, any value in the Errors section may be returned.

Errors:

EAGAIN
The system was unable to allocate a signal handler. This indicated critically low memory.
EFAULT
A fault occurred when the kernel tried to access the buffers provided.
EINVAL
The value of signo is less than 1 or greater than _SIGMAX, or you tried to set SIGKILL or SIGSTOP to something other than SIG_DFL.
EPERM
The calling process doesn't have the required permission; see procmgr_ability().
ESRCH
The process indicated by pid doesn't exist.

Classification:

QNX Neutrino

Safety:  
Cancellation point No
Interrupt handler No
Signal handler Yes
Thread Yes

Last modified: 2014-06-24



Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus