Document ddb.dumpstack sysctl

Remove the mention of ddb.onpanic=2 as that functionality was removed with the
introduction of ddb.dumpstack.

Heads up by <pgoyette>
This commit is contained in:
sevan 2018-02-22 14:37:53 +00:00
parent 80722e99c3
commit 1c253e4545
1 changed files with 6 additions and 3 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: sysctl.7,v 1.122 2018/02/22 14:32:50 sevan Exp $
.\" $NetBSD: sysctl.7,v 1.123 2018/02/22 14:37:53 sevan Exp $
.\"
.\" Copyright (c) 1993
.\" The Regents of the University of California. All rights reserved.
@ -2450,6 +2450,7 @@ privilege may change the value.
.Bl -column "Second level name" "integer" "Changeable" -offset indent
.It Sy Second level name Ta Sy Type Ta Sy Changeable
.It ddb.commandonenter string yes
.It ddb.dumpstack integer yes
.It ddb.fromconsole integer yes
.It ddb.lines integer yes
.It ddb.maxoff integer yes
@ -2463,6 +2464,9 @@ privilege may change the value.
.Bl -tag -width "123456"
.It Li ddb.commandonenter
If not empty, a command to be executed on each enter to the DDB.
.It Li ddb.dumpstack
A value of 1 causes a stack trace to be printed on entering ddb from a panic.
A value of 0 disables this behaviour. The default value is 1.
.It Li ddb.fromconsole ( Dv DDBCTL_FROMCONSOLE )
If not zero, DDB may be entered by sending a break on a serial
console or by a special key sequence on a graphics console.
@ -2474,8 +2478,7 @@ The maximum symbol offset.
The maximum output line width.
.It Li ddb.onpanic ( Dv DDBCTL_ONPANIC )
If greater than zero, DDB will be entered if the kernel panics.
A value of 1 causes the system to enter DDB on panic, while a value of 2
causes the kernel to attempt to print out a stack trace before entering DDB.
A value of 1 causes the system to enter DDB on panic.
A value of 0 causes the kernel to attempt to print a stack trace, then
reboot, while a value of \-1 means neither a stack trace will be printed
nor DDB entered.