From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9997 invoked by alias); 30 Aug 2012 16:05:03 -0000 Received: (qmail 9913 invoked by uid 22791); 30 Aug 2012 16:05:01 -0000 X-SWARE-Spam-Status: No, hits=-6.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_GT X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Aug 2012 16:04:46 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q7UG4gjt002391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 30 Aug 2012 12:04:42 -0400 Received: from host2.jankratochvil.net (ovpn-116-33.ams2.redhat.com [10.36.116.33]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q7UG4cSO026011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 30 Aug 2012 12:04:41 -0400 Date: Thu, 30 Aug 2012 16:05:00 -0000 From: Jan Kratochvil To: Khoo Yit Phang Cc: Hui Zhu , gdb@sourceware.org Subject: Re: Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk") Message-ID: <20120830160438.GA25469@host2.jankratochvil.net> References: <20120719073959.GA10044@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-08/txt/msg00095.txt.bz2 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. 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? Thanks, Jan