mirror of https://github.com/mkerrisk/man-pages
sigaltstack.2: Note that specifying SS_ONSTACK in ss.ss_falgs decreases portability
In the Illumos source (which presumably mirrors its Solaris ancestry), there is this check in the sigaltstack() implementation: if (ss.ss_flags & ~SS_DISABLE) return (set_errno(EINVAL)); And in the FreeBSD source we find similar: if ((ss->ss_flags & ~SS_DISABLE) != 0) return (EINVAL); Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
1f5002208f
commit
e710f10c36
|
@ -273,7 +273,14 @@ On other implementations, and according to POSIX.1,
|
|||
appears only as a reported flag in
|
||||
.IR old_ss.ss_flags .
|
||||
There is no need ever to specify this flag in
|
||||
.IR ss.ss_flags .
|
||||
.IR ss.ss_flags
|
||||
(and indeed, doing so decreases portability,
|
||||
since some implementations
|
||||
.\" See the source code of Illumos and FreeBSD, for example.
|
||||
give an error if
|
||||
.B SS_ONSTACK
|
||||
is specified in
|
||||
.IR ss.ss_flags ).
|
||||
.SH SEE ALSO
|
||||
.BR execve (2),
|
||||
.BR setrlimit (2),
|
||||
|
|
Loading…
Reference in New Issue