Date: Wed, 24 Feb 1999 08:48:17 +0000 (GMT) From: Doug Rabson <dfr@nlsystems.com> To: Joel Ray Holveck <joelh@gnu.org> Cc: Mike Smith <mike@smith.net.au>, current@freebsd.org Subject: Re: NFS Problems Message-ID: <Pine.BSF.4.05.9902240847560.60339-100000@herring.nlsystems.com> In-Reply-To: <86btikdiie.fsf@detlev.UUCP>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 Feb 1999, Joel Ray Holveck wrote: > >> 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. lockinit() takes a wmesg string which is used when a process sleeps on the lock. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 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?Pine.BSF.4.05.9902240847560.60339-100000>