From owner-freebsd-bugs Mon Sep 29 12:07:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA00746 for bugs-outgoing; Mon, 29 Sep 1997 12:07:49 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA00740; Mon, 29 Sep 1997 12:07:30 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id TAA04312; Mon, 29 Sep 1997 19:56:16 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 29 Sep 1997 20:04:41 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199709290905.CAA00880@implode.root.com> References: Your message of "Mon, 29 Sep 1997 16:05:18 +0800." <199709290805.QAA10988@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Sep 1997 19:57:56 +0100 To: dg@root.com, Peter Wemm From: Bob Bishop Subject: Re: kern/4630: buffer_map might become corrupted Cc: Poul-Henning Kamp , Tor Egge , freebsd-bugs@FreeBSD.ORG, dyson@FreeBSD.ORG Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi At 10:05 am +0100 29/9/97, David Greenman wrote: >>BTW2; I wish there was an easy way of producing a stack trace automatically >>on a panic or fatal trap, or as a diagnostic tool. Having a machine panic >>and reboot is near for unattended machines. Having a stack trace in the >>console log would be fantastic. :-) > > John and I were talking about this exact thing just last night. :-) I >think the best approach would be to create a 'cda' crash dump analyzer >that generates a report on reboot (stores the report in a file) that includes >a traceback, register info, dumps of important data structures and lists, etc. >[etc] Isn't that just a (k)gdb script in a wrapper, run after savecore has done its thing? -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK