Date: Wed, 16 Oct 2013 13:42:35 +0100 (BST) From: Anton Shterenlikht <mexas@bris.ac.uk> To: FreeBSD-gnats-submit@freebsd.org Subject: docs/183024: textdump(4) mentions call doadump, should be textdump dump Message-ID: <201310161242.r9GCgZ8Q018250@mech-cluster241.men.bris.ac.uk> Resent-Message-ID: <201310161250.r9GCo03i091645@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 183024
>Category: docs
>Synopsis: textdump(4) mentions call doadump, should be textdump dump
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Oct 16 12:50:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Anton Shterenlikht
>Release: FreeBSD 10.0-CURRENT ia64
>Organization:
Univerisity of Bristol
>Environment:
System: FreeBSD mech-cluster241.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r254648: Thu Aug 22 13:19:48 BST 2013 root@mech-cluster241.men.bris.ac.uk:/usr/obj/usr/src/sys/TZAV ia64
>Description:
This example in textdump(4) is confusing:
script kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
ps; alltrace; show alllocks; call doadump; reset
because it includes "call doadump" with will
create a traditional vmcore* dump.
This command should be replaced with "textdump dump":
script kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
ps; alltrace; show alllocks; textdump dump; reset
Also, when using "call doadump", then "textdump set"
is ignored, and so is TEXTDUMP_PREFERRED kernel option.
This is not clear from the man page.
>How-To-Repeat:
>Fix:
I can make a patch if there is agreement
that my understanding is correct.
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201310161242.r9GCgZ8Q018250>