Date: Mon, 29 Sep 1997 19:57:56 +0100 From: Bob Bishop <rb@gid.co.uk> To: dg@root.com, 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: <l03020904b055a99895cc@[194.32.164.2]> In-Reply-To: <199709290905.CAA00880@implode.root.com> References: 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
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?l03020904b055a99895cc>