This is the mail archive of the
mailing list for the GDB project.
Re: Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk")
- From: Khoo Yit Phang <khooyp at cs dot umd dot edu>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Khoo Yit Phang <khooyp at cs dot umd dot edu>, Hui Zhu <teawater at gmail dot com>, gdb at sourceware dot org
- Date: Thu, 30 Aug 2012 12:08:41 -0400
- 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>
On Aug 30, 2012, at 12:04 PM, Jan Kratochvil wrote:
> On Thu, 30 Aug 2012 18:00:46 +0200, Khoo Yit Phang wrote:
>> I ran into a similar issue as below and tracked it down: the "memory
>> clobbered before allocated block" (and other related messages) because
>> -lmcheck is not thread safe, and triggers spuriously when threads are used
>> in Python (e.g., the "gtk" module).
> this needs some references to glibc/gtk/python maintainers statements etc.
> -lmcheck is AFAIK thread safe in glibc itself.
-lmcheck is definitely not thread safe, at least as of glibc 2.13 (Ubuntu 11.04). See the first answer of http://stackoverflow.com/questions/314931/glibcs-lmcheck-option-and-multithreading.
August 30, 2012