public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/23489] "gcc -lmcheck" aborts on free when using posix_memalign
Date: Thu, 22 Jul 2021 13:20:15 +0000	[thread overview]
Message-ID: <bug-23489-131-NGQDo9NQEA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23489-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23489

Siddhesh Poyarekar <siddhesh at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.34
             Status|ASSIGNED                    |RESOLVED

--- Comment #27 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
commit c142eb253f3814f46527e9b37484041dd85702cf
Author: Siddhesh Poyarekar <siddhesh@sourceware.org>
Date:   Thu Jul 22 18:38:02 2021 +0530

    mcheck: Wean away from malloc hooks [BZ #23489]

    Split the mcheck implementation into the debugging hooks and API so
    that the API can be replicated in libc and libc_malloc_debug.so.  The
    libc APIs always result in failure.

    The mcheck implementation has also been moved entirely into
    libc_malloc_debug.so and with it, all of the hook initialization code
    can now be moved into the debug library.  Now the initialization can
    be done independently of libc internals.

    With this patch, libc_malloc_debug.so can no longer be used with older
    libcs, which is not its goal anyway.  tst-vfork3 breaks due to this
    since it spawns shell scripts, which in turn execute using the system
    glibc.  Move the test to tests-container so that only the built glibc
    is used.

    This move also fixes bugs in the mcheck version of memalign and
    realloc, thus allowing removal of the tests from tests-mcheck
    exclusion list.

    Reviewed-by: Carlos O'Donell <carlos@redhat.com>
    Tested-by: Carlos O'Donell <carlos@redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-07-22 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23489-131@http.sourceware.org/bugzilla/>
2021-07-12 18:04 ` hjl.tools at gmail dot com
2021-07-13 15:46 ` siddhesh at sourceware dot org
2021-07-22 13:20 ` siddhesh at sourceware dot org [this message]
2021-07-22 14:27 ` ht990332 at gmx dot com
2021-07-22 14:34 ` siddhesh at sourceware dot org

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=bug-23489-131-NGQDo9NQEA@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).