Date: Mon, 29 Sep 1997 11:12:03 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: dg@root.com Cc: Peter Wemm <peter@netplex.com.au>, 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: <944.875524323@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 29 Sep 1997 02:05:01 PDT." <199709290905.CAA00880@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199709290905.CAA00880@implode.root.com>, David Greenman writes: >>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. And optionally emails it to some configurable address. >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. Well, if scroll-lock works this is no big loss. >Anyway, this has been on my wishlist for years. mine too. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?944.875524323>