From owner-freebsd-questions@FreeBSD.ORG Mon Feb 7 19:20:50 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D6D016A4CE for ; Mon, 7 Feb 2005 19:20:50 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4451143D3F for ; Mon, 7 Feb 2005 19:20:50 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A171D514FE; Mon, 7 Feb 2005 11:20:49 -0800 (PST) Date: Mon, 7 Feb 2005 11:20:49 -0800 From: Kris Kennaway To: Payment Online Message-ID: <20050207192049.GD3160@xor.obsecurity.org> References: <21fe04a805020711141369e96d@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jCrbxBqMcLqd4mOl" Content-Disposition: inline In-Reply-To: <21fe04a805020711141369e96d@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: FreeBSD Questions Subject: Re: Python with threading core dumps on 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Feb 2005 19:20:50 -0000 --jCrbxBqMcLqd4mOl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Feb 07, 2005 at 11:14:36AM -0800, Payment Online wrote: > I am consistantly getting seg faults and bus errors when running a > multi threaded python application under 5.3-release-p2. Python was > built from the port(python 2.4) with threading enabled. Rebuilding > with the huge stack size option enabled didn't make a difference. The > application uses twisted (www.twistedmatrix.com) and it runs fine > until I put it under a bit of a load and have 20-30 simultaneous > threads running. Then it core dumps. Following is the backtrace from > the core file. The backtrace is always the same. Are threads just > generally problematic on Freebsd? You'll need to recompile with debugging symbols in order to get a useful trace. The python maintainer might be able to talk you through this. Kris > #0 0x2823cdbb in pthread_testcancel () from /usr/lib/libpthread.so.1 > #1 0x28234b06 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 > #2 0x00000000 in ?? () --jCrbxBqMcLqd4mOl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCB7+RWry0BWjoQKURAuaaAJ4gcjcWRae1Ru1rHIxOGUZUqHMAaQCgp4Tk gEe9OGY7gz5LpoLy0qXg4e8= =Lja7 -----END PGP SIGNATURE----- --jCrbxBqMcLqd4mOl--