From owner-freebsd-current Tue Feb 23 11:32:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (45-sweet.camalott.com [208.239.153.45]) by hub.freebsd.org (Postfix) with ESMTP id 10D5C1114F for ; Tue, 23 Feb 1999 11:32:13 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.2/8.9.1) id NAA20337; Tue, 23 Feb 1999 13:31:23 -0600 (CST) (envelope-from joelh) To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: NFS Problems References: <199902222220.OAA00897@dingo.cdrom.com> From: Joel Ray Holveck Date: 23 Feb 1999 13:31:21 -0600 In-Reply-To: Mike Smith's message of "Mon, 22 Feb 1999 14:20:42 -0800" Message-ID: <86btikdiie.fsf@detlev.UUCP> Lines: 25 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This reminds me; do we have a utility to reference wmesg strings back >> to the code that sets them, a la TAGS? Would this be useful? > No, and yes respectively. I have the scanner mostly written; there is one bug yet to fix (This time for sure!). Presently, it creates a single file WTAGS which contains an easily-read (my man or machine) flat file index. I will presently be modifying it to generate Emacs's etags format, as well as ctags, and as soon as I learn it, GSYMS format. At the moment, the scanner scans tsleep, asleep, and ttysleep calls. What other sleep functions can have the wchan specified as a string literal? There being no robust manner to handle calls with a computed or dereferenced wchan, such as acquire(), I will allow for a notation of /* WCHAN: foo */ to cause the appropriate information to be added to the database. Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message