This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk")
- From: Tom Tromey <tromey at redhat dot com>
- To: Khoo Yit Phang <khooyp at cs dot umd dot edu>
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, Hui Zhu <teawater at gmail dot com>, gdb at sourceware dot org
- Date: Thu, 06 Sep 2012 13:29:40 -0600
- Subject: Re: Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk")
- References: <CANFwon0wEXd+40H85veHyRTg+itYyL2jjgsCMYByxk5K0MTLHA@mail.gmail.com> <20120719073959.GA10044@host2.jankratochvil.net> <A681786A-58A1-41E6-8410-8EBD8330E6BE@cs.umd.edu> <20120830160438.GA25469@host2.jankratochvil.net> <41429A68-82EE-4B57-BAB3-559D2907A71B@cs.umd.edu> <2E2CF815-7C3F-40D1-A8FB-CEB190731F20@cs.umd.edu>
>>>>> "Yit" == Khoo Yit Phang <khooyp@cs.umd.edu> writes:
Yit> Here's the corresponding bug report for glibc stating that it is by
Yit> design: http://sourceware.org/bugzilla/show_bug.cgi?id=9939
I asked the local glibc hackers to see if they can fix it.
It seems to me that, while the existing malloc hooks are inherently
broken for multi-threading in the "wrapper" case, there is no deep
reason that mcheck has to use these hooks.
Tom