diff options
Diffstat (limited to 'man2/sigaltstack.2')
| -rw-r--r-- | man2/sigaltstack.2 | 21 |
1 files changed, 13 insertions, 8 deletions
diff --git a/man2/sigaltstack.2 b/man2/sigaltstack.2 index 0214315b11..764ef96f39 100644 --- a/man2/sigaltstack.2 +++ b/man2/sigaltstack.2 @@ -323,6 +323,11 @@ if (sigaction(SIGSEGV, &sa, NULL) == -1) { .EE .in .SH BUGS +In Linux 2.2 and earlier, the only flag that could be specified +in +.I ss.sa_flags +was +.BR SS_DISABLE . In the lead up to the release of the Linux 2.4 kernel, .\" Linux 2.3.40 .\" After quite a bit of web and mail archive searching, @@ -331,13 +336,11 @@ In the lead up to the release of the Linux 2.4 kernel, .\" explained -- mtk a change was made to allow .BR sigaltstack () -to accept -.B SS_ONSTACK -in -.IR ss.ss_flags , -which results in behavior that is the same as when -.I ss_flags -is 0 (i.e., the inclusion of +to allow +.I ss.ss_flags==SS_ONSTACK +with the same meaning as +.IR "ss.ss_flags==0" +(i.e., the inclusion of .B SS_ONSTACK in .I ss.ss_flags @@ -346,7 +349,9 @@ On other implementations, and according to POSIX.1, .B SS_ONSTACK appears only as a reported flag in .IR old_ss.ss_flags . -On Linux, there is no need ever to specify this flag in +On Linux, there is no need ever to specify +.B SS_ONSTACK +in .IR ss.ss_flags , and indeed doing so should be avoided on portability grounds: various other systems |