From owner-freebsd-current@FreeBSD.ORG Sun Jun 2 15:08:58 2013 Return-Path: Delivered-To: FreeBSD-CURRENT@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0874559F; Sun, 2 Jun 2013 15:08:58 +0000 (UTC) (envelope-from daemon@dx.burplex.com) Received: from dx.burplex.com (dx.burplex.com [50.197.134.185]) by mx1.freebsd.org (Postfix) with ESMTP id EA61C1D33; Sun, 2 Jun 2013 15:08:57 +0000 (UTC) Received: by dx.burplex.com (Postfix, from userid 1) id AD2BD36F486E; Sun, 2 Jun 2013 08:08:57 -0700 (PDT) To: Mark Johnston Subject: Re: issue with libthr? From: Waitman Gobble X-UUID-HOR: d55635a9-cb92-11e2-8072-902b34a86bc3 Message-Id: <20130602150857.AD2BD36F486E@dx.burplex.com> Date: Sun, 2 Jun 2013 08:08:57 -0700 (PDT) Cc: FreeBSD-CURRENT@freebsd.org, marcel@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jun 2013 15:08:58 -0000 On Sun, 2 Jun 2013 10:43:35 -0400, Mark Johnston wrote: > >On Sat, Jun 01, 2013 at 12:54:14AM -0700, Waitman Gobble wrote: >> >> Hi, >> >> I'm getting a ton of core dumps from Python and any software that uses Python, >> ie has USE_PYTHON_BUILD=yes in Makefile. >> >> hundreds of msgs in dmesg: >> pid 36637 (seamonkey), uid 1001: exited on signal 11 (core dumped) >> pid 36986 (seamonkey), uid 1001: exited on signal 11 (core dumped) >> pid 37054 (seamonkey), uid 1001: exited on signal 11 (core dumped) >> pid 51780 (seamonkey), uid 1001: exited on signal 11 (core dumped) >> pid 83350 (python2.7), uid 0: exited on signal 6 (core dumped) >> >> from gdb it seems to me to be libthr related? I've noticed a couple updates in >> May.. wonder if it's related? I've only noticed this issue in the past week, >> after a complete rebuild and updated. > >I've been running into this issue too - python 2.7 would crash when >trying to rebuild databases/tdb and databases/py-sqlite3 with backtraces >similar to what you have below. The python port itself hasn't changed in >a while. > >Reverting r250991 and rebuilding libc solves the issue for me: >http://svnweb.freebsd.org/base?view=revision&revision=250991 > >> Thanks for the info, I appreciate it. I had a heck of a time getting database/py-sqlite3 to build as well. My workaround to get it installed was to change the Makefile in WRKSRC try: import ctypes ctypes.CDLL('libsqlite3.so').sqlite3_load_extension except AttributeError: macros.append(('SQLITE_OMIT_LOAD_EXTENSION', '1')) it was bombing out on the 'except AttributeError:' line. So I just changed it to macros.append(('SQLITE_OMIT_LOAD_EXTENSION', '1')) since I didn't have the extensions option SQLITE, if you have that option then just delete the whole block, nothing needed. Of course the 'better' way is to find the source of the issue. :) -- Waitman Gobble San Jose California USA +1.5108307875