In article <3901C85B.5ECE547D@mandrakesoft.com> you wrote:
> One of things of my todo list is to hack lint or a workalike tool, to
> analyze C source code to catch common driver errors...
Hi,
In the past, I used LCLINT to check my kernel code, and (with some minor
issues in include-files) that worked. For the more "high-level" issues,
ITS4 (*) may be the tool to use/change.
Greetings,
Arjan van de Ven
(*) http://www.rstcorp.com/its4/
(Integrates very well into a CVS system with "bonsai" enhancements)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:21 EST