Date: Sun, 2 Oct 2005 22:32:37 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ddb db_command.c Message-ID: <20051002223114.I71864@fledge.watson.org> In-Reply-To: <200510021141.j92BfCKE056337@repoman.freebsd.org> References: <200510021141.j92BfCKE056337@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051002223114.I71864>