aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndriy Gapon <avg@FreeBSD.org>2019-10-18 12:32:01 +0000
committerAndriy Gapon <avg@FreeBSD.org>2019-10-18 12:32:01 +0000
commit47adb0e0e08e272b580d51db9c662f39f9366df7 (patch)
treeb6fe32e13059cf06fd3f702a3037e2b68b28d991
parenta161fba99204b305d02108c94ce5b1eefbf1febc (diff)
downloadsrc-47adb0e0e08e272b580d51db9c662f39f9366df7.tar.gz
src-47adb0e0e08e272b580d51db9c662f39f9366df7.zip
ddb: use 'textdump dump' instead of 'call doadump'
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
Notes
Notes: svn path=/head/; revision=353726
-rw-r--r--sbin/ddb/ddb.conf2
-rw-r--r--share/man/man4/textdump.44
2 files changed, 3 insertions, 3 deletions
diff --git a/sbin/ddb/ddb.conf b/sbin/ddb/ddb.conf
index a793705c6585..1246c0effdf4 100644
--- a/sbin/ddb/ddb.conf
+++ b/sbin/ddb/ddb.conf
@@ -9,7 +9,7 @@
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; call doadump; reset
+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
diff --git a/share/man/man4/textdump.4 b/share/man/man4/textdump.4
index c3c1dcad300a..9b8f88359a4a 100644
--- a/share/man/man4/textdump.4
+++ b/share/man/man4/textdump.4
@@ -27,7 +27,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd November 30, 2018
+.Dd October 18, 2019
.Dt TEXTDUMP 4
.Os
.Sh NAME
@@ -162,7 +162,7 @@ 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=textdump set; capture on; show allpcpu; bt;
- ps; alltrace; show alllocks; call doadump; reset
+ ps; alltrace; show alllocks; textdump dump; reset
.Ed
.Pp
In the following example, the script