1SIGSTACK(2) System Calls Manual SIGSTACK(2)
2
3
4
6 sigstack - set and/or get signal stack context
7
9 #include <signal.h>
10
11 struct sigstack {
12 caddr_t ss_sp;
13 int ss_onstack;
14 };
15
16 sigstack(ss, oss);
17 struct sigstack *ss, *oss;
18
20 This interface has been made obsolete by: [22msigaltstack(2).
21
22 Sigstack allows users to define an alternate stack on which signals are
23 to be processed. If ss is non-zero, it specifies a signal stack on
24 which to deliver signals and tells the system if the process is cur‐
25 rently executing on that stack. When a signal's action indicates its
26 handler should execute on the signal stack (specified with a sigvec(2)
27 call), the system checks to see if the process is currently executing
28 on that stack. If the process is not currently executing on the signal
29 stack, the system arranges a switch to the signal stack for the dura‐
30 tion of the signal handler's execution. If oss is non-zero, the cur‐
31 rent signal stack state is returned.
32
34 Signal stacks are not ``grown'' automatically, as is done for the nor‐
35 mal stack. If the stack overflows unpredictable results may occur.
36
38 Upon successful completion, a value of 0 is returned. Otherwise, a
39 value of -1 is returned and errno is set to indicate the error.
40
42 Sigstack will fail and the signal stack context will remain unchanged
43 if one of the following occurs.
44
45 [EFAULT] Either ss or oss points to memory that is not a valid
46 part of the process address space.
47
49 sigvec(2), setjmp(3)
50
52 The sigstack function call appeared in 4.2BSD and has been deprecated.
53
54
55
564.2 Berkeley Distribution September 3, 1997 SIGSTACK(2)