6c8066b18b
The change is for the example in textdump.4 and the default ddb.conf. First of all, doadump now requires an argument and it won't do a textdump if the argument is not 'true'. And 'textdump dump' is more idiomatic anyway. For what it's worth, ddb 'dump' command seems to always request a vmcore dump even if a textdump was requested earlier, e.g., by 'textdump set'. Finally, ddb 'call' command is not documented. MFC after: 2 weeks
16 lines
506 B
Plaintext
16 lines
506 B
Plaintext
# $FreeBSD$
|
|
#
|
|
# This file is read when going to multi-user and its contents piped thru
|
|
# ``ddb'' to define debugging scripts.
|
|
#
|
|
# see ``man 4 ddb'' and ``man 8 ddb'' for details.
|
|
#
|
|
|
|
script lockinfo=show locks; show alllocks; show lockedvnods
|
|
|
|
# kdb.enter.panic panic(9) was called.
|
|
script kdb.enter.panic=textdump set; capture on; run lockinfo; show pcpu; bt; ps; alltrace; capture off; textdump dump; reset
|
|
|
|
# kdb.enter.witness witness(4) detected a locking error.
|
|
script kdb.enter.witness=run lockinfo
|