From owner-freebsd-threads@FreeBSD.ORG Mon Mar 22 15:31:53 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 6D37D16A4CE for ; Mon, 22 Mar 2004 15:31:53 -0800 (PST) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5211643D2F for ; Mon, 22 Mar 2004 15:31:51 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc11) with ESMTP id <2004032223314601300drf44e>; Mon, 22 Mar 2004 23:31:50 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA39065; Mon, 22 Mar 2004 15:33:00 -0800 (PST) Date: Mon, 22 Mar 2004 15:32:59 -0800 (PST) From: Julian Elischer To: Thomas Hurst In-Reply-To: <20040322175637.GA57230@voi.aagh.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 23:31:53 -0000 On Mon, 22 Mar 2004, Thomas Hurst wrote: > * 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.. :) try the same but using /kernel instead of kernel.debug > > -- > Thomas 'Freaky' Hurst - newzBin Developer & Admin - freaky@newzbin.com >