HP-UX Reference (11i v1 00/12) - 2 System Calls (vol 5)

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man2/!!!intro.2
________________________________________________________________
___ ___
s
sigstack(2) sigstack(2)
(TO BE OBSOLETED)
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() ,orswapcontext() 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.
Threads Considerations
Each thread may define an alternate signal handlingstack.
LWP (Lightweight Processes) Considerations
Each LWP may define an alternate signal handlingstack.
SEE ALSO
exec(2), fork(2), setjmp(3C), sigaltstack(2), <signal.h>.
CHANGE HISTORY
First released in Issue 4, Version 2.
HP-UX Release 11i: December 2000 − 2 − Section 2−−365
___
___