On Feb 7, 2010, at 8:17 PM, Jason Hsu wrote:

> However, splint now refuses to recognize the variables that were  
> declared in the *.h files #included at the beginning of the program.
>
> it only reports the first error it finds and then ignores the rest  
> of the program.

> Is using splint a lost cause for embedded engineering?

It should not be a lost cause.  At least, the problems you are having  
seem like some sort of misconfiguration or bug, rather than the usual  
sort of problems one encounters with static analysis tools in embedded  
environments.  C compilers are relatively infamous for being unable to  
continue parsing source after certain types of errors, and it's not  
very surprising that splint would have similar problems.  I haven't  
used splint itself, and we have an entire "group" that sets up our  
analysis tools (often at great difficulty and with intimate vendor  
involvement), so I can't comment specifically.

Do you have an example C file and command line that you are having  
trouble with?

You might have more immediate benefit by installing gcc and running it  
against your code in its most pedantic and critical modes, with all  
warnings enabled...

BillW

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist