Date: Tue, 27 Jul 2021 21:05:14 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 191607] Inconsistent documentation on entering the debugger Message-ID: <bug-191607-9-vVjYQYCDLx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-191607-9@https.bugs.freebsd.org/bugzilla/> References: <bug-191607-9@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191607 --- Comment #3 from Ed Maste <emaste@freebsd.org> --- We have these sysctls to control behaviour: ebug.debugger_on_trap: Run debugger on kernel trap before panic debug.debugger_on_recursive_panic: Run debugger on recursive kernel panic debug.debugger_on_panic: Run debugger on kernel panic debug.kdb.panic: set to panic the kernel debug.kdb.enter: set to enter the debugger debug.kdb.break_to_debugger: Enable break to debugger debug.kdb.alt_break_to_debugger: Enable alternative break to debugger and these kernel options: # # Don't enter the debugger for a panic. Intended for unattended operation # where you may want to enter the debugger from the console, but still want # the machine to recover from a panic. # options KDB_UNATTENDED # Options for serial drivers that support consoles: options BREAK_TO_DEBUGGER # A BREAK/DBG on the console goes to # ddb, if available. # Solaris implements a new BREAK which is initiated by a character # sequence CR ~ ^b which is similar to a familiar pattern used on # Sun servers by the Remote Console. There are FreeBSD extensions: # CR ~ ^p requests force panic and CR ~ ^r requests a clean reboot. options ALT_BREAK_TO_DEBUGGER --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-191607-9-vVjYQYCDLx>