[Bug 191607] Inconsistent documentation on entering the debugger

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 27 Jul 2021 21:05:14 UTC

--- 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

You are receiving this mail because:
You are the assignee for the bug.