From owner-freebsd-bugs  Mon Sep 29 02:05:01 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA29152
          for bugs-outgoing; Mon, 29 Sep 1997 02:05:01 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA29139;
          Mon, 29 Sep 1997 02:04:55 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA00880;
	Mon, 29 Sep 1997 02:05:01 -0700 (PDT)
Message-Id: <199709290905.CAA00880@implode.root.com>
To: Peter Wemm <peter@netplex.com.au>
cc: Poul-Henning Kamp <phk@critter.freebsd.dk>,
        Tor Egge <Tor.Egge@idi.ntnu.no>, 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 16:05:18 +0800."
             <199709290805.QAA10988@spinner.netplex.com.au> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 29 Sep 1997 02:05:01 -0700
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>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.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project