From owner-freebsd-questions@FreeBSD.ORG Wed Sep 13 23:17:39 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 90B1616A403 for ; Wed, 13 Sep 2006 23:17:39 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53CFC43D49 for ; Wed, 13 Sep 2006 23:17:39 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin03-en2 [10.13.10.148]) by smtpout.mac.com (Xserve/8.12.11/smtpout02/MantshX 4.0) with ESMTP id k8DNHdpJ001712; Wed, 13 Sep 2006 16:17:39 -0700 (PDT) Received: from [17.214.13.96] (a17-214-13-96.apple.com [17.214.13.96]) (authenticated bits=0) by mac.com (Xserve/smtpin03/MantshX 4.0) with ESMTP id k8DNHaNE024935; Wed, 13 Sep 2006 16:17:37 -0700 (PDT) In-Reply-To: <4065CD1E-54D7-49E3-A532-C312450BA101@myamail.com> References: <4065CD1E-54D7-49E3-A532-C312450BA101@myamail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Wed, 13 Sep 2006 16:17:35 -0700 To: Fred C! X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAQAAA+k= X-Language-Identified: TRUE Cc: freebsd-questions@freebsd.org Subject: Re: Problem with sqlite3 and python X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 23:17:39 -0000 On Sep 13, 2006, at 3:48 PM, Fred C! wrote: > Hello I have a problem with Python + sqlite3. My main machine is a > FreeBSD 6.1 I have also try on an old machine running FreeBSD 5.5 > and it doesn't work either. I join to this email some information. > I can also provide a core file if someone is interested in solving > that problem. > > Thanks you for any information on how to solve this Not enough data; switch to the thread which crashed, ie got the SIG 11, and do a "bt" to try to see what was going wrong. Note that debugging multithreaded programs is rather difficult, and you might want to double-check that your basic Python installation is OK first by running the included self-tests which come with the Python distribution. If you're using the Python from ports, try doing: cd /usr/ports/lang/python && make cd /usr/ports/lang/python/work/Python-2.4.3 && make test -- -Chuck