From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9998 invoked by alias); 19 Jul 2012 07:54:38 -0000 Received: (qmail 9986 invoked by uid 22791); 19 Jul 2012 07:54:37 -0000 X-SWARE-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_GT,TW_YG X-Spam-Check-By: sourceware.org Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 19 Jul 2012 07:54:23 +0000 Received: by obhx4 with SMTP id x4so4208326obh.0 for ; Thu, 19 Jul 2012 00:54:23 -0700 (PDT) Received: by 10.60.12.234 with SMTP id b10mr1003271oec.72.1342684463046; Thu, 19 Jul 2012 00:54:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.108.33 with HTTP; Thu, 19 Jul 2012 00:53:42 -0700 (PDT) In-Reply-To: <20120719073959.GA10044@host2.jankratochvil.net> References: <20120719073959.GA10044@host2.jankratochvil.net> From: Hui Zhu Date: Thu, 19 Jul 2012 07:54:00 -0000 Message-ID: Subject: Re: [BUG] gdb crash when "python import gtk" To: Jan Kratochvil Cc: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 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-07/txt/msg00049.txt.bz2 On Thu, Jul 19, 2012 at 3:39 PM, Jan Kratochvil wrote: > Hi Hui, > > On Thu, 19 Jul 2012 09:15:57 +0200, Hui Zhu wrote: >> Without http://sourceware.org/git/?p=gdb.git;a=commit;h=d43ca3bfc165c72be20288233d20d61ec107a2de >> that you committed. > > the problem is apparently the new -lmcheck lightweight memory corruption > testing. > > >> On Thu, Jul 19, 2012 at 1:25 PM, Hui Zhu wrote: >> > GNU gdb (GDB) 7.5.50.20120719-cvs > [...] >> > (gdb) python import gtk >> > memory clobbered before allocated block >> > Aborted (core dumped) > > So the bug is in some gtk code, either the Python binding or the C gtk > implementation itself. > > >> > But in 7.4.1 is OK. > > It did not use -lmcheck so the memory corruption still was there but it was > not shown. > > >> > I think this issue is dangerous because we don't know how much other >> > python modules are affected by this issue. Wish it can be fixed >> > before 7.5 release. > > It will not affect the 7.5 release and neither the 7.5 pre-releases: > [commit/branch] development mode no longer enabled by default > http://sourceware.org/ml/gdb-patches/2012-07/msg00251.html > > On Fedora 17 x86_64 I do not see any problem even with more thorough memory > testing via valgrind: > valgrind ./gdb -ex 'python import gtk' -ex q > pygtk2-2.24.0-4.fc17.x86_64 > gtk2-2.24.10-2.fc17.x86_64 > > So you should file it as pygtk2 bug for the distro you use. > > > Thanks, > Jan OK. Thanks for your help. Report this issue to https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1026487 Thanks, Hui