On Wed, Jan 22, 2003 at 11:13:35PM +0000, D Qi wrote: > I'll take it as splint tools is not suitable for the kernel/driver > development. Is that right from your experience? I don't know splint, but if you can't teach it kernel sources are different from userland sources, it's not suitable. In my opinion 'gcc -Wall' usually does a better job than lint, though some lints (lclint, for example) can track memory allocations. Erik > Erik Mouw wrote: > >On Wed, Jan 22, 2003 at 10:52:01AM +0000, D Qi wrote: > > > >[don't crosspost between lists, this fits best on kernelnewbies] > > > > > >>Which lint tool do you use when you are doing kernel thing? I tried to > >>setup the splint to do some check on my code but encountered quite a lot > >>error, mostly in the source tree includes. Of course I know this is > >>due to my setup of the splint rather than the problem with the kernel > >>source. > > > > > >Lint assumes it has to process userland source, and therefore has some > >assumptions about include files and their contents. The kernel doesn't > >use any userland include file, so lint's assumptions are wrong and > >therefore it will most likely fail. > > > >I've used lclint in the past and I know you can teach it about other > >header files, though it's not easy for a large sourcetree like the > >linux kernel. -- J.A.K. (Erik) Mouw Email: J.A.K.Mouw@its.tudelft.nl mouw@nl.linux.org WWW: http://www-ict.its.tudelft.nl/~erik/
Attachment:
pgp00265.pgp
Description: PGP signature
