[Bug 183024] textdump(4) mentions call doadump, should be textdump dump

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183024

--- Comment #4 from sigsys at gmail.com ---
(In reply to Andriy Gapon from comment #3)
Sure seems like you did!  Thanks.  I forgot to check if it had already been
fixed after finding this PR.

For reference, I just checked if making sure that debug.ddb.textdump.pending is
set or that having "textdump set" in the DDB script is necessary, and it is
not.  "textdump dump" tries to do a textdump no matter what.

I wish the manpage gave some pointer to "debug.debugger_on_panic" though (I had
the KDB_UNATTENDED option when trying to set this up and ddb wasn't being
invoked at all).

Index: share/man/man4/textdump.4
===================================================================
--- share/man/man4/textdump.4   (revision 354599)
+++ share/man/man4/textdump.4   (working copy)
@@ -158,13 +158,21 @@
 .Dv kdb.enter.panic
 will run when the kernel debugger is entered as a result of a panic, enable
 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:
+do a textdump followed by a reboot:
 .Bd -literal -offset indent
 script kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
   ps; alltrace; show alllocks; textdump dump; reset
 .Ed
 .Pp
+Note that
+.Xr ddb 4
+must be set to be invoked on panic for this to work.
+The
+.Dv debug.debugger_on_panic
+sysctl indicates if this is the case
+(it will default to off if the kernel was compiled with
+.Cd options KDB_UNATTENDED ) .
+.Pp
 In the following example, the script
 .Dv kdb.enter.witness
 will run when the kernel debugger is entered as a result of a witness

-- 
You are receiving this mail because:
You are on the CC list for the bug.