[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Experimenting with lclint/splint



Em Tue, Jan 29, 2002 at 03:56:57PM +0100, peteran@ludd.luth.se escreveu:
> Hi,
 
> I just joined this mailing list and thought of checking if anyone was
> alive here. There seems to have been no posts during the last year which
> leads me to believe that either the list has died or that everybody is
> busy auditing.

Well, <plug>you may want to take a look at http://kerneljanitors.org</plug>

8)
 
> What I currently am doing is playing around with lclint, or splint as it
> is now known. There were some great difficulties in the beginning with
> splint barfing over many things, but after getting .splintrc right things
> started to work out a bit better. Most remaining problems have to do with
> gnu extensions and splint not being up to par with C99 (or something).

Nice. I was going to spend some time cooking up a .splintrc as well, so can
you please send me what you have?
 
> Specifically "asm" should be banned (GCC extension) and "__asm"/"__asm__"
> used instead. Same with "inline" <-> "__inline"/"__inline__".  Splint is
> not very happy with those and fails miserably with just reporing a parse
> error. Tracing those to the correct macros was quite an adventure for a
> kernel newbie.

I plan to convert 'inline' to '__inline__' and friends in the KJP

> Most things were quite easily fixed by using e.g. -Dasm=__asm__ in
> .splintrc.  Some were not though resulting in ugly #ifndef S_SPLINT_S
> compiling without splint variant #else stupid splint variant #endif
> 
> Now I am at a point where splint runs quite nicely, but there is one
> little problem. Splint is a memory hog! Running it on all the source in
> the kernel is not recommended.

hey, thats why I got that 512 DDR ram module 8)
 
- Arnaldo
-
Kernel-audit:  discussion list for security and the linux kernel
Archive:       http://mail.nl.linux.org/kernel-audit/