All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
	mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] malloc_hook.3: modernize for glibc 2.34
Date: Sun, 29 Aug 2021 14:34:59 +0200	[thread overview]
Message-ID: <871r6cv37w.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <56b090e7-3b39-7a1d-5e59-1e836eb0cca4@cs.ucla.edu> (Paul Eggert's message of "Fri, 27 Aug 2021 16:34:38 -0700")

* Paul Eggert:

> On 8/27/21 4:11 PM, Alejandro Colomar (man-pages) wrote:
>
>> All good until here.  (Maybe the glibc commit that removed this
>> could go in the commit message, if you know it.)
>
> I don't know it, unfortunately.
>
>>>>   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 ().
>> Did this change with glibc 2.34?
>
> The glibc manual changed (it started documenting this stuff) but this
> part of the implementation did not change.

The documentation is somewhat older than 2.34 and was just minimally
amended.  It's here:

  Replacing malloc
  <https://www.gnu.org/software/libc/manual/html_node/Replacing-malloc.html>

In particular, it lists additional functions that may have to be
interposed due to application use.

Thanks,
Florian


  reply	other threads:[~2021-08-29 12:35 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 [this message]
2021-08-31  1:19   ` [[patch] 2/2] " Michael Kerrisk (man-pages)
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=871r6cv37w.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=alx.manpages@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.