Date: Wed, 26 Dec 2007 23:37:01 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Brian Fundakowski Feldman <green@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf files src/sys/ddb db_command.c db_command.h db_lex.c db_lex.h db_main.c db_script.c ddb.h Message-ID: <20071226233301.K59006@fledge.watson.org> In-Reply-To: <20071226181850.GA6300@green.homeunix.org> References: <200712260933.lBQ9XJi7039100@repoman.freebsd.org> <20071226181850.GA6300@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 26 Dec 2007, Brian Fundakowski Feldman wrote: > Wow, very cool debugging feature! Any more sweet DDB features in the > pipeline? Thanks! DDB capture output, scripting, and textdumps were pretty much what I had in the queue for DDB at this point. I'll see if I can't come up with some stuff, and look forward to hearing about how people use these ones. I'll also happily accept bug reports... Textdumps should open up the door for some interesting things in terms of bug management--I'd love to see someone put together some rc.d/rc.conf parts to do automated crash report submission (disabled by default, of course) and a database to hold the results. I suspect a moderate number of panic reports are lost on the basis that filing a proper bug report is fairly difficult (get out kgdb, etc), or that the boxes quietly reboot and the core dumps rot on disk (to be deleted when space runs out). Perhaps hoovering up those textdumps, especially if we can correlate them with one another using some automated processing, might be quite informative. Or just a good time sink :-). 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?20071226233301.K59006>