diff options
| author | Andriy Gapon <avg@FreeBSD.org> | 2019-10-18 12:32:01 +0000 |
|---|---|---|
| committer | Andriy Gapon <avg@FreeBSD.org> | 2019-10-18 12:32:01 +0000 |
| commit | 47adb0e0e08e272b580d51db9c662f39f9366df7 (patch) | |
| tree | b6fe32e13059cf06fd3f702a3037e2b68b28d991 /sbin | |
| parent | a161fba99204b305d02108c94ce5b1eefbf1febc (diff) | |
| download | src-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
Diffstat (limited to 'sbin')
| -rw-r--r-- | sbin/ddb/ddb.conf | 2 |
1 files changed, 1 insertions, 1 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 |