about summary refs log tree commit diff
path: root/debug
diff options
context:
space:
mode:
authorFlorian Weimer <fweimer@redhat.com>2022-08-03 11:41:53 +0200
committerFlorian Weimer <fweimer@redhat.com>2022-08-03 11:42:39 +0200
commitcca9684f2d7a74fc0b28bfb1859955e0e28d7b4b (patch)
treef07de8d03a36b0d91b7053a88af8d7818b0af20e /debug
parentfccadcdf5bed7ee67a6cef4714e0b477d6c8472c (diff)
downloadglibc-cca9684f2d7a74fc0b28bfb1859955e0e28d7b4b.tar.gz
glibc-cca9684f2d7a74fc0b28bfb1859955e0e28d7b4b.tar.xz
glibc-cca9684f2d7a74fc0b28bfb1859955e0e28d7b4b.zip
stdio: Clean up __libc_message after unconditional abort
Since commit ec2c1fcefb200c6cb7e09553f3c6af8815013d83 ("malloc:
Abort on heap corruption, without a backtrace [BZ #21754]"),
__libc_message always terminates the process.  Since commit
a289ea09ea843ced6e5277c2f2e63c357bc7f9a3 ("Do not print backtraces
on fatal glibc errors"), the backtrace facility has been removed.
Therefore, remove enum __libc_message_action and the action
argument of __libc_message, and mark __libc_message as _No_return.

Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
Diffstat (limited to 'debug')
-rw-r--r--debug/fortify_fail.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/debug/fortify_fail.c b/debug/fortify_fail.c
index b1c51662b7..b880f82cb6 100644
--- a/debug/fortify_fail.c
+++ b/debug/fortify_fail.c
@@ -21,8 +21,6 @@ void
 __attribute__ ((noreturn))
 __fortify_fail (const char *msg)
 {
-  /* The loop is added only to keep gcc happy.  */
-  while (1)
-    __libc_message (do_abort, "*** %s ***: terminated\n", msg);
+  __libc_message ("*** %s ***: terminated\n", msg);
 }
 libc_hidden_def (__fortify_fail)