Hello Paul, On 8/10/21 9:37 PM, Paul Eggert wrote: > --- > man3/malloc_hook.3 | 13 ++++++++++--- > 1 file changed, 10 insertions(+), 3 deletions(-) Patch applied. Thanks you! Cheers, Michael > diff --git a/man3/malloc_hook.3 b/man3/malloc_hook.3 > index 6d944003b..7b76bbc9b 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 > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
