From owner-freebsd-current@FreeBSD.ORG Tue Jun 4 09:10:44 2013 Return-Path: Delivered-To: FreeBSD-CURRENT@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2AEF9A65; Tue, 4 Jun 2013 09:10:44 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) by mx1.freebsd.org (Postfix) with ESMTP id E455F131D; Tue, 4 Jun 2013 09:10:43 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id y10so885247pdj.28 for ; Tue, 04 Jun 2013 02:10:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=bJRkjMMoO9zocfDlTbKdJXDA882Am0wqx6VdANrge1c=; b=Ks+tvfgwK4ZS5pTa2JmT3LbUD27dRC9uHlKBb8CngaykEMhol+DR+DXen0cZa+d4z8 FqYH8OWh+8lynoOxrTVQ4uqYGtz1UXdutTNhc0QnkqpyjCanlzmZMqF6nbZ1Kk5cKakC SnqeNNqYKogOP6YiEqj2ISv5Gu23RMf8yLFSNUD5g/61PKvBYXBMgkNrARLCqtgO9Fok TJ+EF1Ibg4L0kftNEqO3y1EOY3Fyo0Fx0wy5D3LUEkOhzSlLNorl2bXPbWGpyfFDeUIp A47EwIayGTDCrUG9NM680abzWWQGLULcdyEs0y/YOKub43NXVqWLr906AV1s2GbyU3BK AFsw== X-Received: by 10.68.252.227 with SMTP id zv3mr28078841pbc.14.1370337043631; Tue, 04 Jun 2013 02:10:43 -0700 (PDT) Received: from [192.168.1.7] (ppp59-167-128-11.static.internode.on.net. [59.167.128.11]) by mx.google.com with ESMTPSA id nk2sm7958705pbc.43.2013.06.04.02.10.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Jun 2013 02:10:42 -0700 (PDT) Message-ID: <51ADAF05.3090403@FreeBSD.org> Date: Tue, 04 Jun 2013 19:10:29 +1000 From: Kubilay Kocak User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Waitman Gobble Subject: Re: issue with libthr? References: <20130603165444.581F436F49FF@dx.burplex.com> In-Reply-To: <20130603165444.581F436F49FF@dx.burplex.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-CURRENT@freebsd.org, Mark Johnston , marcel@freebsd.org, Marcel Moolenaar X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: koobs@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 09:10:44 -0000 On 4/06/2013 2:54 AM, Waitman Gobble wrote: > On Mon, 3 Jun 2013 07:55:54 -0700, Marcel Moolenaar wrote: > >> >> >> 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 >> >> >> > > > yes, that patch seems to work on my machine. After rebuilding Python with the > patch, I was able to install databases/py-sqlite3 without error, also the > www/midori port now builds and installs without crashing. I'll let you know if > I see any problems. > > Thank you, > Great work Marcel :) What needs to be done to get this upstreamed? Koobs