In case of db_onpanic=0, still drop to ddb if the trap was from within
ddb. i.e. "db> x/s 0x14" should return you to ddb when it faults, regardless of the state of db_onpanic.
This commit is contained in:
parent
cc732067b7
commit
aa0007b5a5
|
@ -1,4 +1,4 @@
|
|||
/* $NetBSD: db_interface.c,v 1.28 2000/01/16 01:42:03 assar Exp $ */
|
||||
/* $NetBSD: db_interface.c,v 1.29 2000/05/15 20:16:48 jhawk Exp $ */
|
||||
|
||||
/*
|
||||
* Mach Operating System
|
||||
|
@ -92,7 +92,7 @@ kdb_trap(type, code, regs)
|
|||
case -1: /* keyboard interrupt */
|
||||
break;
|
||||
default:
|
||||
if (!db_onpanic)
|
||||
if (!db_onpanic && db_recover==0)
|
||||
return (0);
|
||||
|
||||
kdbprinttrap(type, code);
|
||||
|
|
Loading…
Reference in New Issue