From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18756 invoked by alias); 28 Aug 2012 19:45:17 -0000 Received: (qmail 18743 invoked by uid 22791); 28 Aug 2012 19:45:16 -0000 X-SWARE-Spam-Status: No, hits=-6.6 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_BJ 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; Tue, 28 Aug 2012 19:45:02 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q7SJivwC025167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 28 Aug 2012 15:44:57 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q7SJitom006717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 28 Aug 2012 15:44:56 -0400 From: Tom Tromey To: Kevin Pouget Cc: gdb@sourceware.org Subject: Re: GDB crashing because of Python References: <87k3wpr9uy.fsf@fleche.redhat.com> <87sjbdo2z4.fsf@fleche.redhat.com> <87wr0kgumi.fsf@fleche.redhat.com> Date: Tue, 28 Aug 2012 19:45:00 -0000 In-Reply-To: <87wr0kgumi.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 27 Aug 2012 10:36:05 -0600") Message-ID: <87zk5eer7s.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (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-08/txt/msg00090.txt.bz2 Kevin> so based on `git bisect`, it looks like the errors were introduced by Kevin> this commit: Tom> Can you please try the appended patch? I spent some time today trying to make a robust test case for this. I can see the error clearly with valgrind, but I can't make it crash. Printing the Objfile reference counts "works" but it seems to not be very robust -- in the failing case the count appears to be 12 on my machine, but of course this is just a fluke, and it could well be anything. -lmcheck unfortunately doesn't help, because Python is typically built using its own allocator. It would be nice if we could disable this for the test suite -- it is automatically disabled under valgrind (under some typical configurations), so it could be done cheaply -- but this isn't available. Anyway, I'm going to write a ChangeLog and send it to the patch list. Tom