From: Tom Tromey <tromey@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: How important is mcheck?
Date: Tue, 11 Feb 2014 17:05:00 -0000 [thread overview]
Message-ID: <87d2itwpft.fsf@fleche.redhat.com> (raw)
In-Reply-To: <52F8F53C.8090708@redhat.com> (Florian Weimer's message of "Mon, 10 Feb 2014 16:50:20 +0100")
>>>>> "Florian" == Florian Weimer <fweimer@redhat.com> writes:
Florian> I see two bug reports about issues discovered with mcheck, so maybe it
Florian> is useful.
Florian> Could you move mcheck in-tree?
mcheck's been discussed a few times on the gdb lists (I forget which) in
the past; and also at least once on the glibc list.
Some nice things about mcheck are that it is low cost and easy to enable
by default for development builds; since many developers are on
glibc-based systems, it can help catch simpler bugs. As you found it
caught a few in the past.
I suppose we could have main call mcheck. That seems only mildly more
difficult.
Florian> Then you'd be able to enable it regardless of Python threading
Florian> support.
The problem is that mcheck is written in a way that inherently not
thread-safe. This requires a fix in glibc.
Tom
next prev parent reply other threads:[~2014-02-11 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 15:50 Florian Weimer
2014-02-11 17:05 ` Tom Tromey [this message]
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=87d2itwpft.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=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