sigstack - set and/or get alternate signal stack context (LEGACY)
#include <signal.h> int sigstack(struct sigstack *ss, struct sigstack *oss);
The sigstack() function allows the calling process to indicate to the system an area of its address space to be used for processing signals received by the process.
If the ss argument is not a null pointer, it must point to a sigstack structure. The length of the application-supplied stack must be at least SIGSTKSZ bytes. If the alternate signal stack overflows, the resulting behaviour is undefined. (See APPLICATION USAGE below.)
- The value of the ss_onstack member indicates whether the process wants the system to use an alternate signal stack when delivering signals.
- The value of the ss_sp member indicates the desired location of the alternate signal stack area in the process' address space.
- If the ss argument is a null pointer, the current alternate signal stack context is not changed.
If the oss argument is not a null pointer, it points to a sigstack structure in which the current alternate signal stack context is placed. The value stored in the ss_onstack member of oss will be non-zero if the process is currently executing on the alternate signal stack. If the oss argument is a null pointer, the current alternate signal stack context is not returned.
When a signal's action indicates its handler should execute on the alternate signal stack (specified by calling sigaction()), the implementation checks to see if the process is currently executing on that stack. If the process is not currently executing on the alternate signal stack, the system arranges a switch to the alternate signal stack for the duration of the signal handler's execution.
After a successful call to one of the exec functions, there are no alternate signal stacks in the new process image.
This interface need not be reentrant.
Upon successful completion, sigstack() returns 0. Otherwise, it returns -1 and sets errno to indicate the error.
The sigstack() function will fail if:
- An attempt was made to modify an active stack.
A portable application, when being written or rewritten, should use sigaltstack() instead of sigstack().
On some implementations, stack space is automatically extended as needed. On those implementations, automatic extension is typically not available for an alternate stack. If a signal stack overflows, the resulting behaviour of the process is undefined.
The direction of stack growth is not indicated in the historical definition of struct sigstack. The only way to portably establish a stack pointer is for the application to determine stack growth direction, or to allocate a block of storage and set the stack pointer to the middle. The implementation may assume that the size of the signal stack is SIGSTKSZ as found in <signal.h>. An implementation that would like to specify a signal stack size other than SIGSTKSZ should use sigaltstack().
Programs should not use longjmp() to leave a signal handler that is running on a stack established with sigstack(). Doing so may disable future use of the signal stack. For abnormal exit from a signal handler, siglongjmp(), setcontext() or swapcontext() may be used. These functions fully support switching from one stack to another.
The sigstack() function requires the application to have knowledge of the underlying system's stack architecture. For this reason, sigaltstack() is recommended over this function.
exec, fork(), _longjmp(), longjmp(), setjmp(), sigaltstack(), siglongjmp(), sigsetjmp(), <signal.h>.