summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--share/man/man4/ddb.44
-rw-r--r--share/man/man4/textdump.48
2 files changed, 6 insertions, 6 deletions
diff --git a/share/man/man4/ddb.4 b/share/man/man4/ddb.4
index 2caae2d..e9ff506 100644
--- a/share/man/man4/ddb.4
+++ b/share/man/man4/ddb.4
@@ -785,8 +785,8 @@ commands separated with the
character.
For example:
.Bd -literal -offset indent
-script kdb.enter.panic=bt;show pcpu
-script lockinfo=show alllocks;show lockedvnods
+script kdb.enter.panic=bt; show pcpu
+script lockinfo=show alllocks; show lockedvnods
.Ed
.Pp
The
diff --git a/share/man/man4/textdump.4 b/share/man/man4/textdump.4
index 15fe517..b0f002f 100644
--- a/share/man/man4/textdump.4
+++ b/share/man/man4/textdump.4
@@ -27,7 +27,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd 16 December, 2007
+.Dd 26 December, 2007
.Dt textdump 4
.Os
.Sh NAME
@@ -114,7 +114,7 @@ command in
or by setting the
.Dv debug.ddb.textdump.pending
sysctl to 1 using
-.Xr sysctl 8,
+.Xr sysctl 8 ,
it is possible to request that the next dump be a textdump.
.Pp
If at the
@@ -137,8 +137,8 @@ output capture, dump several useful pieces of debugging information, and then
invoke panic in order to force a kernel dump to be written out followed by a
reboot:
.Bd -literal -offset indent
-script kdb.enter.panic=capture on;textdump set;bt;show allpcpu;
- ps;alltrace;show alllock;panic
+script kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
+ ps; alltrace; show alllock; call doadump; reset
.Ed
.Pp
In the following example, the script
OpenPOWER on IntegriCloud