unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v7 3/8] Move malloc hooks into a compat DSO
Date: Fri, 9 Jul 2021 13:43:14 +0530	[thread overview]
Message-ID: <74c790ec-1a38-9d1a-142a-4edbec064e47@sourceware.org> (raw)
In-Reply-To: <87czrrkiyg.fsf@oldenburg.str.redhat.com>

On 7/9/21 1:38 PM, Florian Weimer wrote:
> * Siddhesh Poyarekar:
> 
>> Remove all malloc hook uses from core malloc functions and move it
>> into a new library libc_malloc_debug.so.  With this, the hooks now no
>> longer have any effect on the core library.
>>
>> libc_malloc_debug.so is a malloc interposer that needs to be preloaded
>> to get hooks functionality back so that the debugging features that
>> depend on the hooks, i.e. malloc-check, mcheck and mtrace work again.
>> Without the preloaded DSO these debugging features will be nops.
>> These features will be ported away from hooks in subsequent patches.
>>
>> Similarly, legacy applications that need hooks functionality need to
>> preload libc_malloc_debug.so.
>>
>> The symbols exported by libc_malloc_debug.so are maintained at exactly
>> the same version as libc.so.
>>
>> Finally, static binaries will no longer be able to use malloc
>> debugging features since they cannot preload the debugging DSO.
> 
> Commit subject could be adjusted because the DSO contains more than just
> the hooks.

OK, I'll update it to "Introduce malloc debug DSO"

> This patch needs to update the shlib-versions file on architectures
> which do not use DEFAULT.  For example, on ia64-linux-gnu, there is a
> malloc/check-abi-libc_malloc_debug failure that looks like this:

Thanks, fixed locally.

Siddhesh

  reply	other threads:[~2021-07-09  8:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08 17:43 [PATCH v7 0/8] malloc hooks removal Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 1/8] Remove __after_morecore_hook Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 2/8] Remove __morecore and __default_morecore Siddhesh Poyarekar via Libc-alpha
2021-07-09  6:27   ` Florian Weimer via Libc-alpha
2021-07-09  7:02     ` Siddhesh Poyarekar via Libc-alpha
2021-07-09  7:46       ` Florian Weimer via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 3/8] Move malloc hooks into a compat DSO Siddhesh Poyarekar via Libc-alpha
2021-07-09  8:08   ` Florian Weimer via Libc-alpha
2021-07-09  8:13     ` Siddhesh Poyarekar via Libc-alpha [this message]
2021-07-09  8:17   ` Florian Weimer via Libc-alpha
2021-07-09  9:17     ` Siddhesh Poyarekar via Libc-alpha
2021-07-09  9:22       ` Florian Weimer via Libc-alpha
2021-07-09  8:26   ` Florian Weimer via Libc-alpha
2021-07-09  9:21     ` Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 4/8] mcheck: Wean away from malloc hooks Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 5/8] Simplify __malloc_initialized Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 6/8] mtrace: Wean away from malloc hooks Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 7/8] glibc.malloc.check: " Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 8/8] Remove " Siddhesh Poyarekar via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=74c790ec-1a38-9d1a-142a-4edbec064e47@sourceware.org \
    --to=libc-alpha@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=siddhesh@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).