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: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Khoo Yit Phang <khooyp at cs dot umd dot edu>
- Cc: Hui Zhu <teawater at gmail dot com>, gdb at sourceware dot org
- Date: Thu, 30 Aug 2012 18:04:38 +0200
- 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>
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.
It seems to me rather that python and/or gtk may have some bugs exposed by
-lmcheck. Could you provide a reproducer (with proper versions of all
components and OS) of the problematic behavior?