From 7738652c369aeb5bf067d3e20b8bb32d6de3b272 Mon Sep 17 00:00:00 2001
From: Tom Rhodes <trhodes@FreeBSD.org>
Date: Tue, 22 Jan 2008 17:47:05 +0000
Subject: [PATCH] Replace 'debug.debugger_on_panic=1' with 'debug.kdb.enter=1'
which actually exists. Add a note on forcing a panic using
'debug.kdb.panic=1'.
PR: 111781
---
.../books/developers-handbook/kerneldebug/chapter.sgml | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
index 6d0cf32c98..617bf8f96e 100644
--- a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
+++ b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
@@ -528,7 +528,11 @@
this. If you would like to break to the debugger from the
command prompt, simply type the command:</para>
- <screen>&prompt.root; <userinput>sysctl debug.debugger_on_panic=1</userinput></screen>
+ <screen>&prompt.root; <userinput>sysctl debug.kdb.enter=1</userinput></screen>
+ <note>
+ <para>To force a panic on the fly, issue the following command:</para>
+ <screen>&prompt.root; <userinput>sysctl debug.kdb.panic=1</userinput></screen>
+ </note>
<para>Alternatively, if you are at the system console, you may use
a hot-key on the keyboard. The default break-to-debugger