From owner-freebsd-current@FreeBSD.ORG Mon Jun 3 15:07:59 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 2F8D5A56; Mon, 3 Jun 2013 15:07:59 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by mx1.freebsd.org (Postfix) with ESMTP id E4D371243; Mon, 3 Jun 2013 15:07:58 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id wc20so7406229obb.18 for ; Mon, 03 Jun 2013 08:07:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=7ujv7UvyvIQWbCMfZH8Jrf2NMpyg7Ui637GulEHr98I=; b=EVsZDKVq+i5XkdUyYi9oE78RSiG8oyfbzTt79hOQ984Rht76reT/WsfvKyzrZSbbTE 8l022SR1B4Bk1yZ7PxTKtsb9D1ES2lZUdryVqOka39VrQ1OgVuSbilBlD0/Zc64bJryn FnIPm3LpAUnXlIykP8PGrc/VwmobbKqPsSKVGk77xEES78dyqIFng6kpnd1JUDr5H99i e9b7tEqOk5DVSLQgEIPE8NW0a4gJsrvVBCrmLx+Ughu2MrLq92qN1fU65z/45dPaRSyw Si7dr80JXAgpoqEQBt35yRQpZGot6tIjHQXACF/scQKk3YbkETNPYdEGlhv73fX7uzF+ b97Q== X-Received: by 10.60.33.102 with SMTP id q6mr10476835oei.111.1370272078513; Mon, 03 Jun 2013 08:07:58 -0700 (PDT) Received: from gloom.sandvine.com ([64.7.137.182]) by mx.google.com with ESMTPSA id h4sm48120855oel.2.2013.06.03.08.07.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Jun 2013 08:07:57 -0700 (PDT) Sender: Mark Johnston Date: Mon, 3 Jun 2013 11:07:42 -0400 From: Mark Johnston To: Marcel Moolenaar Subject: Re: issue with libthr? Message-ID: <20130603150742.GA38214@gloom.sandvine.com> References: <20130602150857.AD2BD36F486E@dx.burplex.com> <9E71613B-E904-47AC-813B-54E35B6864A1@xcllnt.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9E71613B-E904-47AC-813B-54E35B6864A1@xcllnt.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Waitman Gobble , 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: Mon, 03 Jun 2013 15:07:59 -0000 On Mon, Jun 03, 2013 at 07:55:54AM -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: > >> > >> 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 > > > 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 > =================================================================== > --- 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 = """ > + src/prep_cif.c > + src/closures.c > +-src/dlmalloc.c > + """.split() > + > + ffi_platforms = { > > > 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. I can confirm that this fixes the problems I had building databases/tdb and databases/py-sqlite3. I haven't done any other testing though. -Mark