-</tr>
-<tr valign=top>
-<td width=135 >
-<a href="http://www.splint.org"><img src="http://www.splint.org/glowingwall-narrows.jpg"
-width=132 height=65 border=0 alt=""></a>
-</td>
-<td>
-<table cellpadding=0 cellspacing=0 width="100%">
-<tr>
-<td colspan=2 bgcolor="slate"></td>
-</tr>
-<tr>
-<td>
-<font color="darkblue" face="arial,helvetica"><a href="http://www.splint.org/"><b>Splint</b> - Secure Programming Lint</a></font>
-</td>
-
-<td align=right>
-<font face="arial,helvetica,sans-serif"><font color="darkblue">
-<font size=-1>
-<a href="mailto:info@splint.org">info@splint.org</a></font>
-</font></font>
-</td>
-</tr>
-
-<tr>
-<td>
-<font face="arial,helvetica,sans-serif" size=-1>
-<a
-href="http://www.splint.org/download.html">Download</a>
--
-<a
-HREF="http://www.splint.org/documentation/">Documentation</a>
-
--
-<a href="http://www.splint.org/manual/">Manual</a>
--
-<a
-href="http://www.splint.org/links.html">Links</a><br>
-
-<a
-href="http://www.splint.org/source.html">Source</a>
--
-<a
-HREF="http://www.splint.org/linux.html">Linux</a>
--
-<a href="http://www.splint.org/pubs.html">Publications</a>
--
-<a
-href="http://www.splint.org/talks.html">Talks</a><br>
-
-</font>
-
-</td>
-<td align=right valign=top>
-
-<font face="arial,helvetica,sans-serif" size=-1>
-<a
-href="http://www.splint.org/bugs.html">Reporting
-Bugs</a> -
-<a
-href="http://www.splint.org/lists.html">Mailing
-Lists</a> <img src="http://sourceforge.net/sflogo.php?group_id=9538" width="0" height="0" alt="">
-
-
-<a
-href="http://www.splint.org/sponsors.html">Sponsors</a>
-
--
-<a
-href="http://www.splint.org/credits.html">Credits</a>
-</font>
-</td>
-</tr>
-
-</table>
-
-</td>
-</tr>
-</table>
-
+ <li>
+ <p><a id="quest10" name="quest10">How does Splint handle const?</a></p>
+ <blockquote>
+ Splint doesn't interpret const (at all). See the manual section on modifies
+ checking (<a
+ href="http://www.splint.org/manual/html/sec7.html">http://www.splint.org/manual/html/sec7.html</a>).<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest11" name="quest11">Why do I get a Warning when multiplying
+ different integer types? The C standard says this is ok. Why is this
+ wrong?</a></p>
+ <blockquote>
+ There are lots of things that the C spec allows and defines clearly, that
+ Splint will provide warnings for. It's not a question of it being "wrong", it's
+ a matter of it being likely to reveal a programming mistake.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest12" name="quest12">The C standard says that what I'm doing is
+ okay. Why does Splint give me a warning?</a></p>
+ <blockquote>
+ See the previous question.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest13" name="quest13">Splint complains if I ignore the return value
+ of scanf but not printf?</a></p>
+ <blockquote>
+ This is just a strategic decision --- we view ignoring the result of a scanf to
+ be more likely to reveal a problem with the code than ignoring the result of a
+ printf, even though strict programmers will want to check printf also.<br />
+ <br />
+
+ <blockquote>
+ If you want stricter checking, use the flags +ansistrictlib, +posixstrictlib,
+ +unixstrictlib to select the strict versions of these libraries.<br />
+ <br />
+ </blockquote>
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest14" name="quest14">I develop code on an embedded system with a
+ compiler that uses nonstandard key words and data types. I would like to run
+ Splint on my code but these nonstandard keywords cause parse errors. What should
+ I do?</a></p>
+ <blockquote>
+ <p>You can often use -D to solve this problem.</p>
+ <p>If you just want to ignore a keyword, you can add -Dnonstandardkeyword= to
+ make the preprocessor eliminate the keyword, where nonstandardkeyword is the
+ name of the keyword. Similarly, you can use -Dspecialtype=int to make a custom
+ type parse as an int.</p>
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest14b" name="quest14b">How can I get Splint to recognize directory
+ trees and local source include directories? I've tried putting them in my path
+ but it doesn't seem to look beyond the current directory.</a></p>
+ <blockquote>
+ You can use -I to set the include path like you would with a compiler.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest15" name="quest15">I heard that we will get lot of parse errors
+ when we run this tool first time. Hence we need to modify source code. Is it
+ correct ?</a></p>
+ <blockquote>
+ Usually not, but Splint doesn't support all C99 extensions.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest16" name="quest16">I heard that Splint can generate some spurious
+ errors ( not genuine errors). Is it correct ?</a></p>
+ <blockquote>
+ Yes, please see <a href="http://www.splint.org/">www.splint.org</a> for
+ details.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest17" name="quest17">When I build Splint I get the following
+ error:</a></p>
+ <blockquote>
+ Checking for...<br />
+ <br />
+
+ <p>Checking manual...</p>
+ <p>cmx > / Checking tests2.2...</p>
+ <p>Checking tests2.4...</p>
+ <p>Checking tests2.5...</p>
+ <p>Checking db1...</p>
+ <p>0a1,2</p>
+ <p>> /cmx/tools/make -e clean</p>
+ <p>> /cmx/tools/make -e check</p>
+ <p>*** FAIL ***</p>
+ <p>Checking db2...</p>
+ <p>0a1,/tools/make -e clean</p>
+ <p>> /cmx/tools/make -e check</p>
+ <p>*** FAIL ***</p>
+ <p>Checking db3...</p>
+ </blockquote>
+ <p>Should I be worried?</p>
+ <blockquote>
+ Those diffs look harmless. It is likely that your make is set up slightly
+ differently than ours.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest18" name="quest18">I just installed Splint on a new machine. I get
+ a bunch of errors during building when the test suite is run. When I look through
+ the results, it seems like Splint is not reporting any errors in the code it
+ analyzes. What is going on?</a></p>
+ <blockquote>
+ One possibility is that the installation directory where the test suite is
+ running is on the system path (hence, splint won't report errors if
+ -sysdirerrors is set, as it is by default). Try adding +sysdirerrors to the
+ command line for the test suite to see if that is the problem, or installing
+ Splint in a different directory not in the system path.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest18b" name="quest18b">I get parse errors when I try to run Splint
+ on code like #define MACROdebug(...) blahblah . Can I use variadic macros in
+ Splint?</a></p>
+ <blockquote>
+ Sorry, Splint does not yet support variadic macros. We hope to fix this in a
+ future release.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest20" name="quest20">I use realloc in my code. How can I get Splint
+ in check this code more effectively?</a></p>
+ <blockquote>
+ realloc has complicated semantics that make it difficult to use correctly. Make
+ sure that you understand realloc and that you really need to use it.<br />
+ <br />
+
+ <p>If you decide to use realloc, we recommend that you wrapper it. The document
+ Using Wrapper Functions explains how to do this. That document is included in
+ the Splint documentation and is also available at:</p>
+ <p><a
+ href="http://www.splint.org/documentation/realloc.htm">http://www.splint.org/documentation/realloc.htm</a></p>
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest21" name="quest21">I think I've found a bug in Splint. What should
+ I do?</a></p>
+ <blockquote>
+ See <a
+ href="http://www.splint.org/bugs.html">http://www.splint.org/bugs.html</a> for
+ a list of known bugs and instructions on reporting bugs.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest22" name="quest22">Splint tells me that there is a bug and I
+ should report it. What information should I send?</a></p>
+ <blockquote>
+ Ideally we would like enough code to reproduce the problem. Small snippets of
+ code which trigger the bug are the best but more code is also acceptable.<br />
+ <br />
+
+ <p>If we're not able to reproduce the problem, then we are unlikely to be able
+ to patch Splint. However, we would still appreciate hearing about the bug and
+ may be able to at least to offer you advice on working around the problem.</p>
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest23" name="quest23">My question isn't answered here. How can I get
+ more information about Splint?</a></p>
+ <blockquote>
+ First check the Splint manual and the mailing list archives.<br />
+ <br />
+
+ <p>The Splint manual is available at: <a
+ href="http://www.splint.org/manual/l">http://www.splint.org/manual/</a></p>
+ <p>The mailing list archives are at:</p>
+ <p><a
+ href="http://www.mail-archive.com/lclint-interest@virginia.edu/u">http://www.mail-archive.com/lclint-interest%40virginia.edu/</a></p>
+ <p>If you're still unable to find the information to answer your question, you
+ can try posting the question to the splint-discuss mailing list (see <a
+ href="http://www.splint.org/lists.html">http://www.splint.org/lists.html</a>)</p>
+ <p>You can also email us at splint@splint.org.</p>
+ </blockquote>
+ </li>
+ </ol>
+ <!--#include virtual="footer.html"-->