From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11729 invoked by alias); 23 Aug 2012 18:52:47 -0000 Received: (qmail 11719 invoked by uid 22791); 23 Aug 2012 18:52:46 -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 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, 23 Aug 2012 18:52:34 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q7NIqXiC023804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Aug 2012 14:52:33 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q7NIqVaL001304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 23 Aug 2012 14:52:32 -0400 From: Tom Tromey To: Kevin Pouget Cc: gdb@sourceware.org Subject: Re: GDB crashing because of Python References: <87k3wpr9uy.fsf@fleche.redhat.com> Date: Thu, 23 Aug 2012 18:52:00 -0000 In-Reply-To: (Kevin Pouget's message of "Thu, 23 Aug 2012 16:29:22 +0200") Message-ID: <87sjbdo2z4.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/msg00081.txt.bz2 Kevin> I'm on Fedora 17, x86_64, Python seems to be at version 2.7.3, gdb is Kevin> up to date against the trunk (7.5.50.20120823-cvs) I installed F17 in a mock chroot and ran the latest gdb there. This isn't an identical scenario due to possible kernel differences, but I wouldn't expect those to matter. >> Fatal Python error: GC object already tracked Kevin> this one appears when I start the inferior execution, and start it again I couldn't make it crash. What happens if you run under valgrind? When I do that, I see some output, but nothing that looks too serious and/or new. Tom