Date: Wed, 6 Aug 2008 09:24:05 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Remko Lodder <remko@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, John Baldwin <jhb@FreeBSD.org> Subject: Re: cvs commit: src/usr.sbin Makefile src/usr.sbin/crashinfo Makefile crashinfo.8 crashinfo.sh Message-ID: <alpine.BSF.1.10.0808060921400.70284@fledge.watson.org> In-Reply-To: <4898BBF1.2080407@FreeBSD.org> References: <200808052042.m75Kg0qZ052029@repoman.freebsd.org> <4898BBF1.2080407@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Aug 2008, Remko Lodder wrote: > John Baldwin wrote: >> jhb 2008-08-05 20:41:46 UTC >> >> FreeBSD src repository >> >> Modified files: >> usr.sbin Makefile Added files: >> usr.sbin/crashinfo Makefile crashinfo.8 crashinfo.sh Log: >> SVN rev 181335 on 2008-08-05 20:41:46Z by jhb >> Add a script to perform simple analysis of a crash dump (either a full >> dump or minidump). When the script is run, it generates a text file >> containing the output of several commands run againt the core dump such >> as kgdb (stack trace), ps, netstat, vmstat, iostat, dmesg, and fstat. >> Obtained from: Yahoo! >> MFC after: 2 weeks > > awesome! This sounds something brilliant we can use for the send-pr stuff :) > > Thanks John! (And Yahoo!) It should also be easy to add a call to ddb(8)'s capture buffer dump routine so that scripted (or unscripted) DDB session output appears in crashinfo output in the same way it appears in textdumps. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.1.10.0808060921400.70284>