public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] manual: SA_ONSTACK is ignored without alternate stack Date: Mon, 28 Feb 2022 12:38:56 +0000 (GMT) [thread overview] Message-ID: <20220228123856.A3DED3858426@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ca7334d34b7811fc261c84c498fd4a19acd70530 commit ca7334d34b7811fc261c84c498fd4a19acd70530 Author: Florian Weimer <fweimer@redhat.com> Date: Mon Feb 28 11:50:41 2022 +0100 manual: SA_ONSTACK is ignored without alternate stack The current stack is used. No SIGILL is generated. Diff: --- manual/signal.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual/signal.texi b/manual/signal.texi index 8a12baf044..5c2ba7dae6 100644 --- a/manual/signal.texi +++ b/manual/signal.texi @@ -1329,7 +1329,7 @@ Setting this flag for a signal other than @code{SIGCHLD} has no effect. If this flag is set for a particular signal number, the system uses the signal stack when delivering that kind of signal. @xref{Signal Stack}. If a signal with this flag arrives and you have not set a signal stack, -the system terminates the program with @code{SIGILL}. +the normal user stack is used instead, as if the flag had not been set. @end deftypevr @deftypevr Macro int SA_RESTART
reply other threads:[~2022-02-28 12:38 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220228123856.A3DED3858426@sourceware.org \ --to=fw@sourceware.org \ --cc=glibc-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).