From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 699 invoked by alias); 6 Sep 2012 19:30:02 -0000 Received: (qmail 607 invoked by uid 22791); 6 Sep 2012 19:30:01 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS 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, 06 Sep 2012 19:29:45 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q86JTgkl026619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Sep 2012 15:29:42 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q86JTeCq005881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 6 Sep 2012 15:29:41 -0400 From: Tom Tromey To: Khoo Yit Phang Cc: Jan Kratochvil , Hui Zhu , gdb@sourceware.org Subject: Re: Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk") References: <20120719073959.GA10044@host2.jankratochvil.net> <20120830160438.GA25469@host2.jankratochvil.net> <41429A68-82EE-4B57-BAB3-559D2907A71B@cs.umd.edu> <2E2CF815-7C3F-40D1-A8FB-CEB190731F20@cs.umd.edu> Date: Thu, 06 Sep 2012 19:30:00 -0000 In-Reply-To: <2E2CF815-7C3F-40D1-A8FB-CEB190731F20@cs.umd.edu> (Khoo Yit Phang's message of "Thu, 30 Aug 2012 12:11:01 -0400") Message-ID: <87txvbj6fv.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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-09/txt/msg00006.txt.bz2 >>>>> "Yit" == Khoo Yit Phang 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