Date: Mon, 5 Jun 1995 07:05:46 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: jgreco@brasil.moneng.mei.com (Joe Greco) Cc: gpalmer@freefall.cdrom.com, hackers@freebsd.org Subject: Re: Kernels, panics & the debugger Message-ID: <199506051405.HAA23295@gndrsh.aac.dev.com> In-Reply-To: <199506051321.IAA06743@brasil.moneng.mei.com> from "Joe Greco" at Jun 5, 95 08:21:04 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Can I suggest yet another flag to be put in the kernel? It seems to > > me that you could want a situation where you want to be able to get > > into the debugger (for machine lock-ups), but you want the machine to > > panic cleanly when you aren't there and leave a core dump instead. > > > > My proposal: a flag which allows <CTRL>-<ALT>-<ESC> to still drop you > > into the debugger, but which doesn't call the debugger > > for kernel panic's. > > > > Comments? > > A kernel variable or something like this would be great; I would really like > to run the debugger on all my systems, but cannot risk it on machines that > must be up 24/7. > > I mentioned this some time ago, but nobody seemed too interested. A ``mentioned'' only gets you so far, it means one of us has to take your ``idea'' and go spend the hour or so to implement it. A well documented, minimized change context diff will get your ideas a lot farther than just a request for them :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506051405.HAA23295>