[PATCH] abort.3: Note that the glibc implementation is not async-signal-safe
From: Tomáš Golembiovský <hidden>
Date: 2023-07-26 11:56:32
Subsystem:
the rest · Maintainer:
Linus Torvalds
See https://sourceware.org/bugzilla/show_bug.cgi?id=26275 Cc: Carlos O'Donell <redacted> Cc: Glibc <redacted> Signed-off-by: Tomáš Golembiovský <redacted> --- man3/abort.3 | 6 ++++++ man7/signal-safety.7 | 5 +++++ 2 files changed, 11 insertions(+)
diff --git a/man3/abort.3 b/man3/abort.3
index 0b57e10ed..827d5c9db 100644
--- a/man3/abort.3
+++ b/man3/abort.3@@ -85,6 +85,12 @@ terminates the process without flushing streams. POSIX.1 permits either possible behavior, saying that .BR abort () "may include an attempt to effect fclose() on all open streams". +.SH BUGS +The glibc implementation of +.BR abort () +is not async-signal-safe, +.\" FIXME . https://sourceware.org/bugzilla/show_bug.cgi?id=26275 +in violation of the requirements of POSIX.1. .SH SEE ALSO .BR gdb (1), .BR sigaction (2),
diff --git a/man7/signal-safety.7 b/man7/signal-safety.7
index 3d6ddc7eb..431a22f89 100644
--- a/man7/signal-safety.7
+++ b/man7/signal-safety.7@@ -335,6 +335,11 @@ The glibc implementation of is not async-signal-safe because it uses .BR pthread_mutex_lock (3) internally. +.IP \[bu] +.\" FIXME . https://sourceware.org/bugzilla/show_bug.cgi?id=26275 +The glibc implementation of +.BR abort (3) +is not async-signal-safe. .SH SEE ALSO .BR sigaction (2), .BR signal (7),
--
2.41.0