From owner-freebsd-current@FreeBSD.ORG Sun Jun 2 04:32:35 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 DB387E3 for ; Sun, 2 Jun 2013 04:32:35 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by mx1.freebsd.org (Postfix) with ESMTP id B81741738 for ; Sun, 2 Jun 2013 04:32:35 +0000 (UTC) Received: by mail-pd0-f177.google.com with SMTP id u11so4092095pdi.22 for ; Sat, 01 Jun 2013 21:32:35 -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=J2oL3blrR7HFiDPZAStfBnVq08ItfuODuVsWEf7/mCE=; b=Wr5pDpPbacuxlKEw9JZiXyATOwcFFXDoDyIzVQtEym7M3Evw42xc1+i6yPw0jgEyen rCxx2C1uV2y2k0NygC0A/q2fxh/OZEOqnluDc6NAjRKOFSPY3LqU2EVAI0+ihtPE2UHE Iqxa0bmB2tCwDf/WHuyeC86muf4MFwEBDmX3ZYu4WKNMBFZgu7onBpLqwQGV9gnT7hDk Ntjmcxi0nEonusCE/NSaCUH/sY5nfO3vGKXLcqh4TJUS7GYBfCdWVvahIRXZLYXWuoHc kDJi2n25Ty4kYPJP3nLIVpsAOfYYBbIJm6REnzBAz8cBILXf5ZRJHv/zMYFrNHi20+Bl Wy7g== X-Received: by 10.68.101.226 with SMTP id fj2mr19398255pbb.6.1370147554947; Sat, 01 Jun 2013 21:32:34 -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 dc3sm15134637pbc.9.2013.06.01.21.32.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 01 Jun 2013 21:32:34 -0700 (PDT) Message-ID: <51AACAD5.4090100@FreeBSD.org> Date: Sun, 02 Jun 2013 14:32:21 +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: <20130602040301.C44A836F49EC@dx.burplex.com> In-Reply-To: <20130602040301.C44A836F49EC@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 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: Sun, 02 Jun 2013 04:32:35 -0000 On 2/06/2013 2:03 PM, Waitman Gobble wrote: > On Sat, 1 Jun 2013 11:14:46 -0700 (PDT), Waitman Gobble > wrote: >> >> On Sat, 1 Jun 2013 20:44:00 +0300, Konstantin Belousov > >> wrote: >>> >>> >>> >>> You cannot even guess what is going on without a proper debug information. >>> Recompile and reinstall the libc/libthr/rtld with the debugging symbols >>> to get proper backtraces. >>> >>> Anyway, two backtraces you demostrated, although not giving much useful >>> data, look very different. More, the second backtrace suggests that >>> there is either a bug in python interposing of malloc or memory > corruption. >> >> >> Thanks so much for your help, I'll rebuild with debug on next. >> > > > Hello, > > Perhaps a better backtrace, from python2.7.core created when trying to install > www/midori > > #0 thr_kill () at thr_kill.S:3 > #1 0x0000000801184ecc in abort () at /usr/src/lib/libc/stdlib/abort.c:65 > #2 0x000000080464aca1 in free (mem=0x8065015b0) > at > /usr/ports/lang/python27/work/Python-2.7.5/Modules/_ctypes/libffi/src/dlmalloc.c:4350 > #3 0x0000000800e4c1af in _pthread_mutex_destroy (mutex= out>) > at /usr/src/lib/libthr/thread/thr_mutex.c:273 > #4 0x00000008010e0def in closedir (dirp=0x803b2dda0) > at /usr/src/lib/libc/gen/closedir.c:65 > #5 0x000000000053d482 in posix_listdir (self=0x0, args=0x806425ae0) > at ./../Modules/posixmodule.c:2543 > #6 0x000000000057fa6e in PyCFunction_Call (func=0x801920080, arg=0x806425ae0, > > kw=0x0) at ./../Objects/methodobject.c:81 > #7 0x00000000004e40dd in call_function (pp_stack=0x7fffffff9388, oparg=1) > at ./../Python/ceval.c:4021 > #8 0x00000000004dffcd in PyEval_EvalFrameEx (f=0x801a8f9a0, throwflag=0) > at ./../Python/ceval.c:2666 > > snipped, complete backtrace at https://dx.burplex.com/backtrace.txt > > > all ports have been rebuilt, lib_pkgchk returns no missing libraries. > running FreeBSD 10.0-CURRENT #0 r251216: Sat Jun 1 03:21:48 PDT 2013 > > It seems that any program using Python crashes. also, Seamonkey. I do not so > far notice > any other issues with this system. It was working great until an update about > a week ago. > > seamonkey > (gdb) bt > #0 thr_kill () at thr_kill.S:3 > #1 0x000000080316b585 in XRE_InstallX11ErrorHandler () > from /usr/local/lib/seamonkey/libxul.so > #2 0x0000000800f75286 in handle_signal (actp=, sig=11, > > info=0x7fffffffb7f0, ucp=0x7fffffffb480) > at /usr/src/lib/libthr/thread/thr_sig.c:237 > #3 0x0000000800f74e89 in thr_sighandler (sig=11, info=, > > _ucp=) at /usr/src/lib/libthr/thread/thr_sig.c:182 > #4 0x00007ffffffff1d3 in ?? () > #5 0x0000000800f74d70 in sigaction () > at /usr/src/lib/libthr/thread/thr_sig.c:574 > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently asm > > > Thank you. I wonder if Pythons regression test picks anything up: ./python -m test.regrtest Run that in $WRKSRC/portbld.static/ after building