From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>,
linux-man@vger.kernel.org, alx.manpages@gmail.com
Cc: mtk.manpages@gmail.com
Subject: Re: [[patch] 2/2] malloc_hook.3: modernize for glibc 2.34
Date: Tue, 31 Aug 2021 03:19:12 +0200 [thread overview]
Message-ID: <37d6bb42-5a83-6ef7-e17b-26fbd5a0e671@gmail.com> (raw)
In-Reply-To: <20210810193708.10277-2-eggert@cs.ucla.edu>
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/
next prev parent reply other threads:[~2021-08-31 1:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 19:37 [[patch] 1/2] malloc.3: modernize for glibc 2.34 Paul Eggert
2021-08-10 19:37 ` [[patch] 2/2] malloc_hook.3: " Paul Eggert
2021-08-27 22:04 ` [PATCH] " Paul Eggert
2021-08-27 23:11 ` Alejandro Colomar (man-pages)
2021-08-27 23:34 ` Paul Eggert
2021-08-29 12:34 ` Florian Weimer
2021-08-31 1:19 ` Michael Kerrisk (man-pages) [this message]
2021-08-27 22:02 ` [PATCH] malloc.3: modernize for glibc 2.34 (ping 1) Paul Eggert
2021-08-27 23:07 ` Alejandro Colomar (man-pages)
2021-08-27 23:29 ` Paul Eggert
2021-08-31 1:18 ` [[patch] 1/2] malloc.3: modernize for glibc 2.34 Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37d6bb42-5a83-6ef7-e17b-26fbd5a0e671@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).