From owner-freebsd-questions@FreeBSD.ORG Mon Feb 7 19:14:38 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 9A5C616A4CE for ; Mon, 7 Feb 2005 19:14:38 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id C515243D41 for ; Mon, 7 Feb 2005 19:14:37 +0000 (GMT) (envelope-from snacktime2@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so756643wra for ; Mon, 07 Feb 2005 11:14:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=GxBZwBduMKWMBzuSHlBtcBsqCGdwV6QFlt978ibYqyzm1srFzbm/AhSlg9fELMnV9GE1g4YnvQQZTBPBkPQ4HvXNtoVfMjMPINRCkjI47qLOhOtjXwPWqg4dJcT45lQiplQ2SntCM/E7IBOnNAxa2dOsY3Nq07JhjAP/xItSWqI= Received: by 10.54.52.75 with SMTP id z75mr153917wrz; Mon, 07 Feb 2005 11:14:36 -0800 (PST) Received: by 10.54.40.24 with HTTP; Mon, 7 Feb 2005 11:14:36 -0800 (PST) Message-ID: <21fe04a805020711141369e96d@mail.gmail.com> Date: Mon, 7 Feb 2005 11:14:36 -0800 From: Payment Online To: FreeBSD Questions Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Python with threading core dumps on 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Payment Online List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Feb 2005 19:14:38 -0000 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? #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 ?? ()