d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Minor formatting tweaks; recommend "call doadump; reset" over "panic"

Browse Source 
from a script as the DDB panic command is unreliable.

MFC after:	3 months
This commit is contained in:
rwatson 2007-12-26 12:18:21 +00:00
parent 63408299ff
commit ce2b35c358
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
share/man/man4/ddb.4
View File

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

8
share/man/man4/textdump.4
View File

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