From owner-freebsd-doc@FreeBSD.ORG Fri May 30 19:00:01 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org 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 ESMTPS id 67FEE51F for ; Fri, 30 May 2014 19:00:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55DBE25A0 for ; Fri, 30 May 2014 19:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4UJ01Ea076610 for ; Fri, 30 May 2014 19:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4UJ01Td076609; Fri, 30 May 2014 19:00:01 GMT (envelope-from gnats) Date: Fri, 30 May 2014 19:00:01 GMT Message-Id: <201405301900.s4UJ01Td076609@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: Sevan Janiyan Subject: Re: docs/183024: textdump(4) mentions call doadump, should be textdump dump Reply-To: Sevan Janiyan X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 May 2014 19:00:01 -0000 The following reply was made to PR docs/183024; it has been noted by GNATS. From: Sevan Janiyan 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