From owner-cvs-src@FreeBSD.ORG Thu Oct 27 05:58:48 2005 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4AEE16A41F; Thu, 27 Oct 2005 05:58:48 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2F1D43D45; Thu, 27 Oct 2005 05:58:47 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id j9R5wko3004116; Thu, 27 Oct 2005 15:58:46 +1000 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id j9R5witV014561; Thu, 27 Oct 2005 15:58:45 +1000 Date: Thu, 27 Oct 2005 15:58:44 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Peter Wemm In-Reply-To: <200510262240.j9QMe7l0011003@repoman.freebsd.org> Message-ID: <20051027155314.A24293@delplex.bde.org> References: <200510262240.j9QMe7l0011003@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern subr_kdb.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2005 05:58:49 -0000 On Wed, 26 Oct 2005, Peter Wemm wrote: > peter 2005-10-26 22:40:07 UTC > > FreeBSD src repository > > Modified files: > sys/kern subr_kdb.c > Log: > Commit something we found useful at work at one point. Add sysctls for > debug.kdb.panic and debug.kdb.trap alongside the existing debug.kdb.enter > sysctl. 'panic' causes a panic, and 'trap' causes a page fault. We used > these to ensure that crash dumps succeed from those two common failure > modes. This avoids the need for creating a 'panic' kld module. This has nothing to do with kdb, so it doesn't belong here. Panics and traps just happen to invoke a debugger if a debugger is configured. Panics should have even less to do with kdb -- the existence of the panic command in ddb is a bug, since debugger context is special and not suitable for calling panic(); e.g., sync() in panic() only ever worked because of other bugs (ddb keeps^Wkept interrupts disabled but sync() requires interrupts to do i/o). Bruce