From owner-freebsd-threads@FreeBSD.ORG Mon Mar 22 09:56:45 2004 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 57EBB16A4CE for ; Mon, 22 Mar 2004 09:56:45 -0800 (PST) Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6F9743D2D for ; Mon, 22 Mar 2004 09:56:44 -0800 (PST) (envelope-from tom@hur.st) Received: from voi.aagh.net ([81.104.55.176]) by mta01-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP id <20040322175626.IWGE2185.mta01-svc.ntlworld.com@voi.aagh.net>; Mon, 22 Mar 2004 17:56:26 +0000 Received: from freaky by voi.aagh.net with local (Exim 4.30; FreeBSD) id 1B5TfB-000Ewu-3a; Mon, 22 Mar 2004 17:56:37 +0000 Date: Mon, 22 Mar 2004 17:56:37 +0000 From: Thomas Hurst To: Julian Elischer Message-ID: <20040322175637.GA57230@voi.aagh.net> Mail-Followup-To: Julian Elischer , threads@freebsd.org References: <20040322170816.GA56747@voi.aagh.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Not much. User-Agent: Mutt/1.5.6i Sender: Thomas Hurst cc: threads@freebsd.org Subject: Re: Loaded MySQL 4.0.18 w/ KSE running nicely 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: Mon, 22 Mar 2004 17:56:45 -0000 * Julian Elischer (julian@elischer.org) wrote: > I'm guessing that you don't have a debug kernel or a core dump right? You guess right; we'll make one and use that before we try to reproduce though. > The big difference between 5.2.1 and -current is that (assuming you > select the BSD4 scheduler) the threads code has been cleaned up > somewhat. Some edge cases have been cleened up for example. Hehe, my collegue says "cleaned up, broke, what's the difference ;)" > a core-dump would be great however! Well, hopefully we won't have one, or it'll mean we managed to crash again.. but otherwise sure ;) > failing that you could do: (if you have a kernel.debug in your build > tree) > > gdb -k kernel.debug /dev/mem > > x/i 0xc061e937 > > and see what function the pagefault occured in No kernel.debug either; sorry. Nice idea though; I'll remember that :) > even without the kernel.debug there MAY be enough info in /kernel > to give us a clue. I'm listening.. :) -- Thomas 'Freaky' Hurst - newzBin Developer & Admin - freaky@newzbin.com