From owner-freebsd-hackers Mon Jun 5 06:21:37 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA29768 for hackers-outgoing; Mon, 5 Jun 1995 06:21:37 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA29762 ; Mon, 5 Jun 1995 06:21:36 -0700 Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id IAA06743; Mon, 5 Jun 1995 08:21:05 -0500 From: Joe Greco Message-Id: <199506051321.IAA06743@brasil.moneng.mei.com> Subject: Re: Kernels, panics & the debugger To: gpalmer@freefall.cdrom.com (Gary Palmer) Date: Mon, 5 Jun 1995 08:21:04 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: <199506051229.FAA24756@freefall.cdrom.com> from "Gary Palmer" at Jun 5, 95 05:29:51 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: hackers-owner@freebsd.org Precedence: bulk > 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 -- 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. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847