Date: 23 Feb 1999 13:31:21 -0600 From: Joel Ray Holveck <joelh@gnu.org> To: Mike Smith <mike@smith.net.au> Cc: current@FreeBSD.ORG Subject: Re: NFS Problems Message-ID: <86btikdiie.fsf@detlev.UUCP> In-Reply-To: Mike Smith's message of "Mon, 22 Feb 1999 14:20:42 -0800" References: <199902222220.OAA00897@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86btikdiie.fsf>