This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: How important is mcheck?
- From: Florian Weimer <fweimer at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb at sourceware dot org
- Date: Tue, 11 Feb 2014 22:27:53 +0100
- Subject: Re: How important is mcheck?
- Authentication-results: sourceware.org; auth=none
- References: <52F8F53C dot 8090708 at redhat dot com> <87d2itwpft dot fsf at fleche dot redhat dot 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