From: Khoo Yit Phang <khooyp@cs.umd.edu>
To: Khoo Yit Phang <khooyp@cs.umd.edu>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Hui Zhu <teawater@gmail.com>,
gdb@sourceware.org
Subject: Re: Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk")
Date: Thu, 30 Aug 2012 16:11:00 -0000 [thread overview]
Message-ID: <2E2CF815-7C3F-40D1-A8FB-CEB190731F20@cs.umd.edu> (raw)
In-Reply-To: <41429A68-82EE-4B57-BAB3-559D2907A71B@cs.umd.edu>
Hi,
Here's the corresponding bug report for glibc stating that it is by design: http://sourceware.org/bugzilla/show_bug.cgi?id=9939
Yit
August 30, 2012
On Aug 30, 2012, at 12:08 PM, Khoo Yit Phang wrote:
> Hi,
>
> On Aug 30, 2012, at 12:04 PM, Jan Kratochvil wrote:
>
>> Hi,
>>
>> 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.
>
> Yit
> August 30, 2012
next prev parent reply other threads:[~2012-08-30 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 5:26 [BUG] gdb crash when "python import gtk" Hui Zhu
2012-07-19 7:16 ` Hui Zhu
2012-07-19 7:21 ` Phil Muldoon
2012-07-19 7:40 ` Jan Kratochvil
2012-07-19 7:54 ` Hui Zhu
[not found] ` <A681786A-58A1-41E6-8410-8EBD8330E6BE@cs.umd.edu>
2012-08-30 16:05 ` Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk") Jan Kratochvil
2012-08-30 16:07 ` Jan Kratochvil
2012-08-30 16:09 ` Khoo Yit Phang
2012-08-30 16:11 ` Khoo Yit Phang [this message]
2012-08-30 16:41 ` Khoo Yit Phang
2012-09-06 19:30 ` Tom Tromey
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=2E2CF815-7C3F-40D1-A8FB-CEB190731F20@cs.umd.edu \
--to=khooyp@cs.umd.edu \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=teawater@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).