> From: splint-discuss-boun...@cs.virginia.edu [mailto:splint-discuss-
> boun...@cs.virginia.edu] On Behalf Of A Z
> Sent: Monday, 15 March, 2010 04:12
> 
> Guys
> Just started to use splint in IDE of  Visual C++ 2008 Expression
> Edition and its not working.

Using it under an IDE may not be the best plan. You'll have an easier
time controlling the command line and environment running Splint from a
console window.

> When I execute splint it gives me the following log.Sorry for
including
> this long log here.
> 
> [
> Command Line: Cannot open options file: C:\Program
>   There was a problem reading an initialization file (Use -warnrc to
inhibit
>   warning)
> Command Line: Unrecognized file extension:
>     Files\splint-3.1.1\bin\.splintrc (assuming .splintrc is C source
code)
>   warn when command line file does not have a recognized extension
(Use
>   -fileextensions to inhibit warning)

You have spacey path names on the Splint command line, and they're not
quoted.

Here, the problem is a command line like:

     splint -f C:\Program Files\splint-3.1.1\bin\.splintrc

Like all good programs, splint uses spaces as delimiters on its command
line, so it reads that as "-f C:\Program", followed by another argument
that's "Files\splint-3.1.1\bin\.splintrc".

Arguments with spaces in the name need to be quoted:

     splint -f "c:\program files\splint-3.1.1\bin\.splintrc"

Even better, do not use spacey paths, as they are a brain-dead
convention introduced by Microsoft to make everyone's life harder.
Install Splint in a sensible, spaceless path, and keep your sources in a
similar one.

> C:\include\vadefs.h(52,26): Datatype uintptr_t declared with
> inconsistent type:
>                                unsigned int
>   A function, variable or constant is redefined with a different type.
> (Use
>   -incondefs to inhibit warning)
>    load file standard.lcd: Specification of uintptr_t: unsigned int *

These other errors could be cascades from the failure to load your
.splintrc, or they could be real problems with your source. There's no
way for us to tell, since we cannot psychically see what in your source
is producing them.

-- 
Michael Wojcik
Principal Software Systems Developer, Micro Focus


_______________________________________________
splint-discuss mailing list
splint-discuss@mail.cs.virginia.edu
http://www.cs.virginia.edu/mailman/listinfo/splint-discuss

Reply via email to