From: Paul Eggert <eggert@cs.ucla.edu>
Date: Tue, 10 Aug 2021 19:37:08 +0000 (-0700)
Subject: malloc_hook.3: Modernize for glibc 2.34
X-Git-Tag: man-pages-5.19-rc1~894
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ddc5192f0caaaa79f1d32cd6b729a23c8140989f;p=thirdparty%2Fman-pages.git

malloc_hook.3: Modernize for glibc 2.34

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---

diff --git a/man3/malloc_hook.3 b/man3/malloc_hook.3
index 6d944003b8..7b76bbc9b4 100644
--- a/man3/malloc_hook.3
+++ b/man3/malloc_hook.3
@@ -11,7 +11,7 @@
 .SH NAME
 __malloc_hook, __malloc_initialize_hook,
 __memalign_hook, __free_hook, __realloc_hook,
-__after_morecore_hook \- malloc debugging variables
+__after_morecore_hook \- malloc debugging variables (DEPRECATED)
 .SH SYNOPSIS
 .nf
 .B "#include <malloc.h>"
@@ -86,11 +86,18 @@ The use of these hook functions is not safe in multithreaded programs,
 and they are now deprecated.
 From glibc 2.24 onwards, the
 .B __malloc_initialize_hook
-variable has been removed from the API.
+variable has been removed from the API,
+and from glibc 2.34 onwards, all
+the hook variables have been removed from the API.
 .\" https://bugzilla.redhat.com/show_bug.cgi?id=450187
 .\" http://sourceware.org/bugzilla/show_bug.cgi?id=9957
 Programmers should instead preempt calls to the relevant functions
-by defining and exporting functions such as "malloc" and "free".
+by defining and exporting
+.BR malloc (),
+.BR free (),
+.BR realloc (),
+and
+.BR calloc ().
 .SH EXAMPLES
 Here is a short example of how to use these variables.
 .PP