Suggested by Paul Eggert in
<https://lists.gnu.org/archive/html/bug-gnulib/2024-07/msg00154.html>.
* lib/stdlib.in.h (abort): Add comment.
* doc/stack-trace.texi: Document what to do in signal handlers.
+2024-07-18 Bruno Haible <bruno@clisp.org>
+
+ abort-debug: Document better.
+ Suggested by Paul Eggert in
+ <https://lists.gnu.org/archive/html/bug-gnulib/2024-07/msg00154.html>.
+ * lib/stdlib.in.h (abort): Add comment.
+ * doc/stack-trace.texi: Document what to do in signal handlers.
+
2024-07-18 Alejandro Colomar <alx@kernel.org>
xstrtol: Strengthen sanity check.
Thus, @code{abort ()} remains the idiom of choice
for signaling a fatal situation that requires developer attention:
it is useful both in debugging environments and production code.
+
+Note:
+While the original @code{abort} function is safe to call in signal handlers,
+the overridden @code{abort} function is not.
+In signal handlers, you will need to call the original @code{abort} function,
+by doing @code{#undef abort} first.
#if @GNULIB_ABORT_DEBUG@
+/* Terminates the current process with signal SIGABRT.
+ Note: While the original abort() function is safe to call in signal handlers,
+ the overridden abort() function is not. */
# if @REPLACE_ABORT@
# if !(defined __cplusplus && defined GNULIB_NAMESPACE)
# undef abort