From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 5 15:22:32 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E78ADD7 for ; Thu, 5 Mar 2015 15:22:32 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 06D617E9 for ; Thu, 5 Mar 2015 15:22:32 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 14CFFB97B; Thu, 5 Mar 2015 10:22:31 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: Glitch with textdump/ddb Date: Thu, 05 Mar 2015 10:04:33 -0500 Message-ID: <1935444.uB8LrzP6Br@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 05 Mar 2015 10:22:31 -0500 (EST) Cc: Shrikanth Kamath X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Mar 2015 15:22:32 -0000 On Wednesday, March 04, 2015 01:06:17 AM Shrikanth Kamath wrote: > But if I change the script to > ddb script kdb.enter.panic="textdump set; capture on; show pcpu; ps; > call doadump(1)" > > The value supplied to call doadump when the machine enters debugger > on panic is now set to '1'. > > Should this be the right way to capture information when using text > dumps? I guess the man page for textdump specifies just "call > doadump". The problem may not manifest as long the random value picked > off the stack is non zero. Yes, the value should be passed explicitly. HEAD now has a 'dump' command that is preferred to calling doadump directly though. (Not sure if that command has been merged to any stable branches.) -- John Baldwin