From mexas@bristol.ac.uk  Wed Oct 16 12:43:02 2013
Return-Path: <mexas@bristol.ac.uk>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by hub.freebsd.org (Postfix) with ESMTP id 8FEC1E99
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 16 Oct 2013 12:43:02 +0000 (UTC)
	(envelope-from mexas@bristol.ac.uk)
Received: from eu1sys200aog122.obsmtp.com (eu1sys200aog122.obsmtp.com [207.126.144.153])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.freebsd.org (Postfix) with ESMTPS id E79542A74
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 16 Oct 2013 12:43:01 +0000 (UTC)
Received: from mail-we0-f169.google.com ([74.125.82.169]) (using TLSv1) by eu1sys200aob122.postini.com ([207.126.147.11]) with SMTP
	ID DSNKUl6JwJzRKOaW2fXSAVizLbFN9S9eOglD@postini.com; Wed, 16 Oct 2013 12:43:02 UTC
Received: by mail-we0-f169.google.com with SMTP id q58so643355wes.0
        for <FreeBSD-gnats-submit@freebsd.org>; Wed, 16 Oct 2013 05:42:40 -0700 (PDT)
Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241])
        by mx.google.com with ESMTPSA id s4sm5603146wiy.1.2013.10.16.05.42.37
        for <FreeBSD-gnats-submit@freebsd.org>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 16 Oct 2013 05:42:39 -0700 (PDT)
Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1])
	by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r9GCgaoo018251
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 16 Oct 2013 13:42:36 +0100 (BST)
	(envelope-from mexas@mech-cluster241.men.bris.ac.uk)
Received: (from mexas@localhost)
	by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r9GCgZ8Q018250;
	Wed, 16 Oct 2013 13:42:35 +0100 (BST)
	(envelope-from mexas)
Message-Id: <201310161242.r9GCgZ8Q018250@mech-cluster241.men.bris.ac.uk>
Date: Wed, 16 Oct 2013 13:42:35 +0100 (BST)
From: Anton Shterenlikht <mexas@bris.ac.uk>
Sender: Anton Shterenlikht <mexas@bristol.ac.uk>
Reply-To: Anton Shterenlikht <mexas@bris.ac.uk>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: textdump(4) mentions call doadump, should be textdump dump
X-Send-Pr-Version: 3.114
X-GNATS-Notify:

>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:  Fri May 30 19:00:00 UTC 2014
>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:

From: Sevan Janiyan <venture37@geeklan.co.uk>
To: bug-followup@FreeBSD.org, mexas@bris.ac.uk
Cc:  
Subject: Re: docs/183024: textdump(4) mentions call doadump, should be textdump
 dump
Date: Fri, 30 May 2014 19:56:47 +0100

 Hi, the configuration section states:
 
 "By default, kernel dumps generated on panic or	via explicit requests 
 for a dump will be regular memory dumps; how-ever, by using the	textdump 
 set command in	ddb(4),	or by setting the debug.ddb.textdump.pending 
 sysctl to 1 using sysctl(8), it is possible to request that the next 
 dump be a textdump."
 
 when you call doadump, the textdump is created, it's not possible to set 
 the type after requesting a dump because the dump happens there & then 
 on call.
 
 On 10.0-RELEASE TEXTDUMP_PREFERRED is honored.
 Entering the debugger & running call doadump outputs
 textdump: creating 'ddb.txt'.
 textdump: creating 'config.txt'.
 textdump: creating 'msgbuf.txt'.
 textdump: creating 'msgbuf.txt'.
 textdump: creating 'version.txt'.
 Textdump complete.
 = 0
>Unformatted:
