From owner-freebsd-current@FreeBSD.ORG Mon Jun 3 14:56:06 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 D378E667; Mon, 3 Jun 2013 14:56:06 +0000 (UTC) (envelope-from marcel@xcllnt.net) Received: from mail.xcllnt.net (mail.xcllnt.net [70.36.220.4]) by mx1.freebsd.org (Postfix) with ESMTP id 97F1C1176; Mon, 3 Jun 2013 14:56:06 +0000 (UTC) Received: from sladejones-sslvpn-nc.jnpr.net (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mail.xcllnt.net (8.14.7/8.14.7) with ESMTP id r53Etwkt028174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 3 Jun 2013 07:55:59 -0700 (PDT) (envelope-from marcel@xcllnt.net) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: issue with libthr? From: Marcel Moolenaar In-Reply-To: <20130602150857.AD2BD36F486E@dx.burplex.com> Date: Mon, 3 Jun 2013 07:55:54 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <9E71613B-E904-47AC-813B-54E35B6864A1@xcllnt.net> References: <20130602150857.AD2BD36F486E@dx.burplex.com> To: Waitman Gobble X-Mailer: Apple Mail (2.1503) Cc: Mark Johnston , marcel@freebsd.org, FreeBSD-CURRENT@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: Mon, 03 Jun 2013 14:56:06 -0000 On Jun 2, 2013, at 8:08 AM, Waitman Gobble = wrote: > On Sun, 2 Jun 2013 10:43:35 -0400, Mark Johnston = wrote:=20 >>=20 >> On Sat, Jun 01, 2013 at 12:54:14AM -0700, Waitman Gobble wrote: >>>=20 >>> Hi, >>>=20 >>> I'm getting a ton of core dumps from Python and any software that = uses > Python, >>> ie has USE_PYTHON_BUILD=3Dyes in Makefile. >>>=20 >>> 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) >>>=20 >>> 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. >>=20 >> 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. >>=20 >> Reverting r250991 and rebuilding libc solves the issue for me: >> http://svnweb.freebsd.org/base?view=3Drevision&revision=3D250991 >>=20 >>>=20 >=20 > Thanks for the info, I appreciate it. I had a heck of a time getting > database/py-sqlite3 to build as well.=20 > My workaround to get it installed was to change the Makefile in WRKSRC Can you apply the following patch to /usr/ports/lang/python27, rebuild python, re-install and then try to build databases/py-sqlite3 again? Index: files/patch-Modules-_ctypes-libffi-fficonfig.py.in =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- files/patch-Modules-_ctypes-libffi-fficonfig.py.in (revision 0) +++ files/patch-Modules-_ctypes-libffi-fficonfig.py.in (working copy) @@ -0,0 +1,10 @@ +--- Modules/_ctypes/libffi/fficonfig.py.in.orig 2013-06-03 = 07:16:44.000000000 -0700 ++++ Modules/_ctypes/libffi/fficonfig.py.in 2013-06-03 = 07:17:03.000000000 -0700 +@@ -1,7 +1,6 @@ + ffi_sources =3D """ + src/prep_cif.c + src/closures.c +-src/dlmalloc.c + """.split() +=20 + ffi_platforms =3D { It seems the root cause is a broken python build that accidentally defines malloc(), free(), at al in _ctypes.so. A longer explanation was sent to svn-src-head@ and svn-src-all@ I expect that the patch also fixes the other problems mentioned in this thread. It would be great if people can verify this. FYI, --=20 Marcel Moolenaar marcel@xcllnt.net