From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 5 15:22:33 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 05444DD8 for ; Thu, 5 Mar 2015 15:22:33 +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 D1CFA7EA 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 C17A1B981; Thu, 5 Mar 2015 10:22:31 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: DDB Improvements Date: Thu, 05 Mar 2015 10:02:51 -0500 Message-ID: <4592683.iJopXWX9Je@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <54F5BE20.2020400@selasky.org> References: <54F5BE20.2020400@selasky.org> 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: Hans Petter Selasky , Daniel Lovasko 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:33 -0000 On Tuesday, March 03, 2015 02:58:56 PM Hans Petter Selasky wrote: > On 03/03/15 14:54, Daniel Lovasko wrote: > > Hello hackers, > > > > I would like to reach out to all DDB users here: what are the things > > (or just one single thing) that you would like to improve in DDB? > > Ranging from UI to code quality, missing features to obsoleted > > features. > > Hi, > > When there are multiple cores, an easy way to see the complete backtrace > of the other cores, and not only the panicing one? tr doesn't work for you? (You can use 'show pcpu ' or 'show all pcpu' to figure out curthread for CPU and then pass that tid or pid to 'tr') -- John Baldwin