From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6135 invoked by alias); 23 Aug 2012 13:21:53 -0000 Received: (qmail 6126 invoked by uid 22791); 23 Aug 2012 13:21:52 -0000 X-SWARE-Spam-Status: No, hits=-3.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-vb0-f41.google.com (HELO mail-vb0-f41.google.com) (209.85.212.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Aug 2012 13:21:35 +0000 Received: by vbkv13 with SMTP id v13so874132vbk.0 for ; Thu, 23 Aug 2012 06:21:34 -0700 (PDT) Received: by 10.52.175.130 with SMTP id ca2mr198580vdc.112.1345728094683; Thu, 23 Aug 2012 06:21:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.96.78 with HTTP; Thu, 23 Aug 2012 06:21:13 -0700 (PDT) From: Kevin Pouget Date: Thu, 23 Aug 2012 13:21:00 -0000 Message-ID: Subject: GDB crashing because of Python To: 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-08/txt/msg00078.txt.bz2 Hello, I notice today a lot for GDB crash because of Python, am I the only one? (I didn't refresh my git tree since a while, so it might not be directly related to the last Python patches) It's hard to tell exactly what cause it, but for instance I see repeatedly: > SystemError: /builddir/build/BUILD/Python-2.7.3/Objects/listobject.c:178: bad argument to internal function This one aborts() GDB > Fatal Python error: GC object already tracked from > #2 0x0000003f2c4f7b3e in Py_FatalError (msg=msg@entry= > 0x3f2c520ae8 "GC object already tracked") > at /usr/src/debug/Python-2.7.3/Python/pythonrun.c:1685 > #3 0x0000003f2c4739cb in PyList_New (size=size@entry=0) > at /usr/src/debug/Python-2.7.3/Objects/listobject.c:170 > #4 0x0000003f2c4f58a5 in PyArena_New () > at /usr/src/debug/Python-2.7.3/Python/pyarena.c:143 > #5 0x0000003f2c4f793a in PyRun_FileExFlags (...) and this one raises a segfault: > Program received signal SIGSEGV, Segmentation fault. > PyObject_Malloc (nbytes=32) > at /usr/src/debug/Python-2.7.3/Objects/obmalloc.c:784 > 784 if ((pool->freeblock = *(block **)bp) != NULL) { from: > #0 PyObject_Malloc (nbytes=32) > at /usr/src/debug/Python-2.7.3/Objects/obmalloc.c:784 > #1 0x0000003f2c475291 in _PyLong_New (size=1) > at /usr/src/debug/Python-2.7.3/Objects/longobject.c:76 > #2 0x0000003f2c479e9f in PyLong_FromUnsignedLongLong ( > ival=ival@entry=135084326) > at /usr/src/debug/Python-2.7.3/Objects/longobject.c:883 > #3 0x00000000004df100 in frapy_pc (self= > , args=) > at ../../../git/gdb/gdb/python/py-frame.c:209 > #4 0x0000003f2c4dce36 in call_function (oparg=, > pp_stack=0x7fff850c3638) > at /usr/src/debug/Python-2.7.3/Python/ceval.c:4082 > #5 PyEval_EvalFrameEx (f=f@entry= I'm on Fedora 17, x86_64, Python seems to be at version 2.7.3, gdb is up to date against the trunk (7.5.50.20120823-cvs) Cordially, Kevin