Date: Mon, 7 Feb 2005 11:20:49 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Payment Online <snacktime2@gmail.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Python with threading core dumps on 5.3 Message-ID: <20050207192049.GD3160@xor.obsecurity.org> In-Reply-To: <21fe04a805020711141369e96d@mail.gmail.com> References: <21fe04a805020711141369e96d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050207192049.GD3160>