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 malloc/18654] mcheck should warn if threads exist
Date: Wed, 14 Jul 2021 02:54:38 +0000 [thread overview]
Message-ID: <bug-18654-131-5Hv5unFHoq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18654-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18654
Siddhesh Poyarekar <siddhesh at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |siddhesh at sourceware dot org
--- Comment #1 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
mcheck and MALLOC_CHECK_ are distinct debugging features. MALLOC_CHECK_ is
fine, it's mcheck that doesn't work well with threads. Given the general
brokenness of mcheck, I am inclined towards gradually pulling the plug on it.
Newer targets don't even have __malloc_initialize_hook that is needed to make
-lmcheck work.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-07-14 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 12:04 [Bug libc/18654] New: " jan.kratochvil at redhat dot com
2015-08-22 21:34 ` [Bug malloc/18654] " jsm28 at gcc dot gnu.org
2021-07-14 2:54 ` siddhesh at sourceware dot org [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=bug-18654-131-5Hv5unFHoq@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).