Date: Mon, 29 Sep 1997 02:05:01 -0700 From: David Greenman <dg@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 Message-ID: <199709290905.CAA00880@implode.root.com> In-Reply-To: Your message of "Mon, 29 Sep 1997 16:05:18 %2B0800." <199709290805.QAA10988@spinner.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709290905.CAA00880>