From owner-freebsd-bugs Mon Sep 29 02:39:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA00795 for bugs-outgoing; Mon, 29 Sep 1997 02:39:40 -0700 (PDT) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA00790; Mon, 29 Sep 1997 02:39:30 -0700 (PDT) Received: from spinner.netplex.com.au (localhost.dialix.com.au [127.0.0.1]) by spinner.netplex.com.au with ESMTP id RAA11950; Mon, 29 Sep 1997 17:38:23 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199709290938.RAA11950@spinner.netplex.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: dg@root.com cc: Poul-Henning Kamp , Tor Egge , freebsd-bugs@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: kern/4630: buffer_map might become corrupted In-reply-to: Your message of "Mon, 29 Sep 1997 02:05:01 MST." <199709290905.CAA00880@implode.root.com> Date: Mon, 29 Sep 1997 17:38:22 +0800 From: Peter Wemm Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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 . > The alternative is to try to output a traceback on the console at crash time, > but this is likely going to scroll other important information off the screen . > Anyway, this has been on my wishlist for years. Careful David, your VMS stripes are showing through again.. :-) Seriously though, it would be wonderful. I liked the interactive SVR4 crash(8M) program too, but it lacked extensibility. However, the other problem is that most of the crashes that I see these days usually prevent a crashdump from happening in the first place, leaving the savecore nothing to work with. cda couldn't do anything in for most of the crashes I see on 2.2. > -DG Cheers, -Peter -- Peter Wemm Netplex Consulting