Default DDB_ONPANIC to zero. The end product is ultimately for the

consumption of users external to the project, users who are unlikely to
be kernel hackers with the motivation to debug crashes. In this situation
rebooting and creating a crash dump is more appropriate than interrupting
normal service for an unbounded amount of time, while also leaving the
machine at cryptic db> prompt.
This commit is contained in:
ad 2009-01-30 21:30:56 +00:00
parent 42356a10b5
commit 6e89a762d6
1 changed files with 3 additions and 3 deletions

View File

@ -1,4 +1,4 @@
/* $NetBSD: db_variables.c,v 1.39 2007/02/22 04:38:06 matt Exp $ */
/* $NetBSD: db_variables.c,v 1.40 2009/01/30 21:30:56 ad Exp $ */
/*
* Mach Operating System
@ -27,7 +27,7 @@
*/
#include <sys/cdefs.h>
__KERNEL_RCSID(0, "$NetBSD: db_variables.c,v 1.39 2007/02/22 04:38:06 matt Exp $");
__KERNEL_RCSID(0, "$NetBSD: db_variables.c,v 1.40 2009/01/30 21:30:56 ad Exp $");
#include "opt_ddbparam.h"
@ -53,7 +53,7 @@ __KERNEL_RCSID(0, "$NetBSD: db_variables.c,v 1.39 2007/02/22 04:38:06 matt Exp $
* panics. Initialize it so that it's patchable.
*/
#ifndef DDB_ONPANIC
#define DDB_ONPANIC 1
#define DDB_ONPANIC 0
#endif
int db_onpanic = DDB_ONPANIC;