From: Florian Weimer <fweimer@redhat.com>
To: gdb@sourceware.org
Subject: How important is mcheck?
Date: Mon, 10 Feb 2014 15:50:00 -0000 [thread overview]
Message-ID: <52F8F53C.8090708@redhat.com> (raw)
GDB enables mcheck if available, unless Python with threading support is
built in (which most distributions do). I've proposed to deprecate
mcheck in glibc, with a goal towards eventually replacing it with stubs
unavailable to newly compiled programs. GDB would still run (and
compile), albeit without mcheck support.
I see two bug reports about issues discovered with mcheck, so maybe it
is useful.
Could you move mcheck in-tree? Then you'd be able to enable it
regardless of Python threading support.
--
Florian Weimer / Red Hat Product Security Team
next reply other threads:[~2014-02-10 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 15:50 Florian Weimer [this message]
2014-02-11 17:05 ` Tom Tromey
2014-02-11 21:28 ` Florian Weimer
2014-02-11 21:44 ` Tom Tromey
2014-02-11 18:27 ` Jan Kratochvil
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=52F8F53C.8090708@redhat.com \
--to=fweimer@redhat.com \
--cc=gdb@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