From: Florian Weimer <fweimer@redhat.com>
To: SuHsueyu via Libc-help <libc-help@sourceware.org>
Cc: SuHsueyu <anolasc13@gmail.com>
Subject: Re: How to hook malloc call?
Date: Sun, 15 Jan 2023 14:00:15 +0100 [thread overview]
Message-ID: <87lem4ar6o.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAEc2n-uL+HuVyeOJp_hB-jV_=nEXMfqepaWo7OjxVwav=zu3aw@mail.gmail.com> (SuHsueyu via Libc-help's message of "Sun, 15 Jan 2023 00:32:19 +0800")
* SuHsueyu via Libc-help:
> Try use __malloc_hook, __free_hook, but these seem to be deprecated in
> glibc 2.35. Is there a new way to hook the malloc call?
Please see:
Replacing malloc
<https://www.gnu.org/software/libc/manual/html_node/Replacing-malloc.html>
You can supply your own malloc implementation.
Thanks,
Florian
prev parent reply other threads:[~2023-01-15 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 16:32 SuHsueyu
2023-01-15 13:00 ` Florian Weimer [this message]
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=87lem4ar6o.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=anolasc13@gmail.com \
--cc=libc-help@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).