From owner-freebsd-hackers Mon Nov 15 8: 3:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id A6DF51509E for ; Mon, 15 Nov 1999 08:03:12 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id LAA11327 for ; Mon, 15 Nov 1999 11:03:06 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id LAA13052 for ; Mon, 15 Nov 1999 11:03:05 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id LAA04493 for freebsd-hackers@freebsd.org; Mon, 15 Nov 1999 11:03:04 -0500 (EST) Date: Mon, 15 Nov 1999 11:03:04 -0500 (EST) From: Thomas David Rivers Message-Id: <199911151603.LAA04493@lakes.dignus.com> To: freebsd-hackers@freebsd.org Subject: Kernel debug assistance? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to track down a problem in 3.3-RELEASE (which I _think_ might be a linux emu bug that's crashing the kernel.) Anyway - I thought I might ask here for some kernel debugging assistance... I've got a debuggable kernel, with DDB. When the panic occurs (which I can readily reproduce) I drop down into DDB... Which is great - right? But - IP is 0x0 (or, sometimes 0x80000000) - so the trace command in DDB (to show the stack traceback) doesn't seem to work - all I get is the Trap 12 message. Does anyone have any sage words of advice on how to proceed with tracking this down? At least some neat trick for determining where the bad branch is taken? - Thanks - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message