From: Florian Weimer <fweimer@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: How important is mcheck?
Date: Tue, 11 Feb 2014 21:28:00 -0000 [thread overview]
Message-ID: <52FA95D9.2090500@redhat.com> (raw)
In-Reply-To: <87d2itwpft.fsf@fleche.redhat.com>
On 02/11/2014 06:04 PM, Tom Tromey wrote:
> I suppose we could have main call mcheck. That seems only mildly more
> difficult.
I would make it completely unavailable.
> 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.
I somewhat naively assumed that GDB uses the xmalloc function variants
consistently, but that doesn't seem to be the case. If it did, just
hooking the x* functions would do the trick.
--
Florian Weimer / Red Hat Product Security Team
next prev parent reply other threads:[~2014-02-11 21:28 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
2014-02-11 21:28 ` Florian Weimer [this message]
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=52FA95D9.2090500@redhat.com \
--to=fweimer@redhat.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.com \
/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