From owner-cvs-src@FreeBSD.ORG Sun Oct 2 21:32:40 2005 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 124FE16A41F; Sun, 2 Oct 2005 21:32:40 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25D8643D49; Sun, 2 Oct 2005 21:32:38 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id F24E546B2D; Sun, 2 Oct 2005 17:32:37 -0400 (EDT) Date: Sun, 2 Oct 2005 22:32:37 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org In-Reply-To: <200510021141.j92BfCKE056337@repoman.freebsd.org> Message-ID: <20051002223114.I71864@fledge.watson.org> References: <200510021141.j92BfCKE056337@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: cvs commit: src/sys/ddb db_command.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 21:32:40 -0000 On Sun, 2 Oct 2005, Robert Watson wrote: > rwatson 2005-10-02 11:41:12 UTC > > FreeBSD src repository > > Modified files: > sys/ddb db_command.c > Log: > Add a DDB "traceall" function, which stack traces all known process > threads. This is quite useful if generating a debug log for post-mortem > by another developer, in which case the person at the console may not > know which threads are of interest. The output of this can be quite > long. > > Discussed with: kris > MFC after: 3 days I wasn't sure how to hook up the DDB paging code to it, so didn't. Or at least, I tried what seemed obvious (copy and paste from db_ps.c) and it didn't work for me. If someone else would like to hook up the DDB pager, that would be great. BTW, when I glanced at the DDB paging code, I noticed that &quit is passed into the setup routine, but didn't actually see a teardown. This is probably because I didn't look very hard, but if it's actually the case that &quit is never unregistered, that might result in stack stomping...? Robert N M Watson