From owner-freebsd-arch@FreeBSD.ORG Wed Jul 30 14:33:06 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A79E37B408; Wed, 30 Jul 2003 14:33:06 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7E7843FBD; Wed, 30 Jul 2003 14:33:05 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([12.233.125.100]) by attbi.com (rwcrmhc13) with ESMTP id <2003073021330401500c7a8re>; Wed, 30 Jul 2003 21:33:04 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA25060; Wed, 30 Jul 2003 14:33:03 -0700 (PDT) Date: Wed, 30 Jul 2003 14:33:01 -0700 (PDT) From: Julian Elischer To: John Baldwin In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: arch@FreeBSD.org Subject: Re: Make long ddb not suck X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2003 21:33:06 -0000 On Wed, 30 Jul 2003, John Baldwin wrote: > I have a patch that adds a simple paging facility to ddb at the > db_printf() level using a one-shot callback mechanism. It includes > a simple paging callback that rearms itself based on the users > input (space does another page, enter another line). I've used this > facility to replace the hand-rolled paging in 'ps', 'show pci', and > 'show ktr'. The patch is at http://www.FreeBSD.org/~jhb/patches/ddb.patch > > Comments? > > Also, I notice that we have a 'show threads' command commented out from > the original Mach sources. I think we should change 'ps' back to just > showing simple process info (and hopefully back to 80 cols) and only > print thread info for 'show threads'. Maybe show threads should take a > PID as the argument? we do have "show thread (addr)" that shows the stacktrace. "show threads {pid}" would be good to identify the address of the thread to examine.. > > Thus, one would have: > > db> ps > 1 blah blah sleeping on "foo" > 2 blah blah threaded > > db> show threads 2 > 0 blah blah sleeping on "bar" > 1 blah blah running on cpuX > currently ps shows the threads by default.. either way is ok I guess. > etc. > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >