From owner-freebsd-threads@FreeBSD.ORG Thu Feb 17 20:51:06 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64B3016A4CE for ; Thu, 17 Feb 2005 20:51:06 +0000 (GMT) Received: from gigave.com (mail.gigave.com [38.113.228.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39DA743D54 for ; Thu, 17 Feb 2005 20:51:06 +0000 (GMT) (envelope-from sean@sean.gigave.com) Received: from sean.gigave.com [38.113.228.242](9y9eg58l122ukuc0)by gigave.comwith esmtp(Exim 4.43 #1 (Gentoo Linux))id 1D1shX-0006QE-Vo; Thu, 17 Feb 2005 12:56:43 -0800 Received: by sean.gigave.com (Postfix, from userid 1001) id 0FF47116FC; Thu, 17 Feb 2005 12:51:06 -0800 (PST) Date: Thu, 17 Feb 2005 12:51:06 -0800 From: Sean Chittenden To: Ion-Mihai Tetcu Message-ID: <20050217205106.GD60630@sean.gigave.com> References: <20050211001252.GY1060@sean.gigave.com> <20050217171456.4b3c4db5@it.buh.cameradicommercio.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050217171456.4b3c4db5@it.buh.cameradicommercio.ro> User-Agent: Mutt/1.5.6i cc: threads@FreeBSD.org Subject: Re: Strange backtrace from amd64 + mysqld... X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 20:51:06 -0000 > I have problems with mail/dspam-devel on amd64 and only if I run it in > daemon mode (stand-alone it doesn't use threads). It doesn't crash, just > spans the threads and stay there. I can say if it's the app or the > system. > If someone could tell me what tool to use (valgrind works only on i386) > I'd be glad to debug further. > > The system is a 5.3-REALEASE and MySQL is 4.1.9 compiled (for now) with > defaults, MyIsam tables (tried inodb but it was way to slow) and had no > mysql problems so far. Try setting the process up to use libthr instead of libpthreads via libmap.conf(5). If that fixes your problems, it's a good bet there's some kind of synchronization issue on amd64 that you're running into. -sc -- Sean Chittenden