-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<link rel="stylesheet" type="text/css" href="http://www.splint.org/splint.css" title="style1">
-
-
- <html xmlns="http://www.w3.org/1999/xhtml">
- <title>Splint FAQ</title>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator"
content="HTML Tidy for Linux/x86 (vers 1st November 2002), see www.w3.org" />
- <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8" />
- <title></title>
+ <link rel="stylesheet" type="text/css" href="http://www.splint.org/splint.css"
+ title="style1" />
+ <title>Splint FAQ</title>
</head>
- <body lang="en-US">
-<table border="0" rules="none" bgcolor="#FFFFFF" width="95%" align=center cellpadding=0 cellspacing=0>
-<tr>
-<td colspan=2 bgcolor="#FFFFFF"></td>
-</tr>
-<tr>
-<td colspan=2 bgcolor="#FFFFFF"></td>
-</tr>
-<tr>
-
-<td colspan=2 bgcolor="#FFFFFF"></td>
-</tr>
-<tr>
-<td colspan=2 bgcolor="#FFFFFF"></td>
-</tr>
-<tr>
-<td colspan=2 bgcolor="#FFFFFF"></td>
-</tr>
-<tr>
-<td colspan=2 bgcolor="#FFFFFF"></td>
-</tr>
-<tr>
-<td>
-<font color="darkblue" face="arial,helvetica"><a href="http://www.splint.org/"><b>Splint</b> - Secure Programming Lint</a><br></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 colspan=2 bgcolor="darkblue"></td>
-</tr>
-<tr>
-<td colspan=2 bgcolor="darkblue"></td>
-</tr>
-<tr>
-<td colspan=2 bgcolor="white"></td>
-
-</tr>
-<tr>
-<td colspan=2 bgcolor="slate"></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>
-
-</font>
-</td>
-<td align=right>
-<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>
-<a
-href="http://www.splint.org/sponsors.html">Sponsors</a>
--
-<a
-href="http://www.splint.org/credits.html">Credits</a>
-</font>
-</td>
-
-</tr>
-</table>
-
+ <body>
+ <!--#include virtual="header.html"-->
<h1>Splint - Frequently Asked Questions</h1>
-
- <h3>Index</h3><ol><li><a href="#quest1"><p>What is the difference between Splint and LCLint?</p>
+ <h3>Index</h3>
+
+ <ol>
+ <h4>General Questions About Splint</h4>
+ <li>
+ <a href="#quest1">
+ What is the difference between Splint and LCLint?</a><br />
+ </li>
+ <li><a href="#quest2">What is the Splint logo?<br />
</a></li>
- <p><li><a href="#quest2">What is the Splint logo?</p>
+ <li><a href="#quest3">Can I include Splint in my software distribution?<br />
</a></li>
- <p><li><a href="#quest3">Can I include Splint in my software distribution?</p>
+ <li><a href="#quest4">Can we use your software in our company? (We are not a GNU
+ organization.)<br />
</a></li>
- <p><li><a href="#quest4">Can we use your software in our company? (We are not a GNU organization.)</p>
+ <li><a href="#quest5">Does Splint handle C++?<br />
</a></li>
- <p><li><a href="#quest5">Does Splint handle C++?</p>
+
+ <h4> Installation</h4>
+ <li><a href="#quest6">I downloaded the Splint .tgz file but can't figure out how to
+ extract it. There is no 'z' option on the tar on my system.<br />
</a></li>
- <p><li><a href="#quest6">I downloaded the Splint .tgz file but can't figure out how to extract it.
- There is no 'z' option on the tar on my system.</p>
+ <li><a href="#quest7">I want to use Splint in win2000. How do I do that?<br />
</a></li>
- <p><li><a href="#quest7">I want to use Splint in win2000. How do I do that?</p>
+ <li><a href="#quest8">I have installed Splint for Windows 2000. Where should I put
+ the ".splintrc" file?<br />
</a></li>
- <p><li><a href="#quest8">I have installed Splint for Windows 2000. Where should I put the ".splintrc"
- file?</p>
+ <h4>Usage</h4>
+ <li><a href="#quest9">Which compilers does Splint support?<br />
</a></li>
- <p><li><a href="#quest9">Which compilers does Splint support?</p>
+ <li><a href="#quest10">How does Splint handle const?<br />
</a></li>
- <p><li><a href="#quest10">How does Splint handle const?</p>
+ <li><a href="#quest11">Why do I get a warning when multiplying different integer
+ types? The C standard says this is ok. Why is this wrong?<br />
</a></li>
- <p><li><a href="#quest11">Why do I get a warning when multiplying different integer types? The C
- standard says this is ok. Why is this wrong?</p>
+ <li><a href="#quest12">The C standard says that what I'm doing is okay. Why does
+ Splint give me a warning?<br />
</a></li>
- <p><li><a href="#quest12">The C standard says that what I'm doing is okay. Why does Splint give me a
- warning?</p>
+ <li><a href="#quest13">Splint complains if I ignore the return value of scanf but
+ not printf?<br />
</a></li>
- <p><li><a href="#quest13">Splint complains if I ignore the return value of scanf but not printf?</p>
+ <li><a href="#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?<br />
</a></li>
- <p><li><a href="#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?</p>
+ <li><a href="#quest14b">How can I get Splint to recognize directory trees and local
+ source include directories?<br />
</a></li>
- <p><li><a href="#quest14b">How can I get Splint to recognize directory trees and local source include
- directories?</p>
+ <li><a href="#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 ?<br />
</a></li>
- <p><li><a href="#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 ?</p>
- </a></li>
- <p><li><a href="#quest16">I heard that Splint can generate some spurious errors ( not genuine errors).
- Is it correct ?</p>
+ <li><a href="#quest16">I heard that Splint can generate some spurious errors ( not
+ genuine errors). Is it correct ?<br />
</a></li>
- <p><li><a href="#quest17">When I build Splint I get the following errors.... Should I be worried?</p>
+ <li><a href="#quest17">When I build Splint I get the following errors.... Should I
+ be worried?<br />
</a></li>
- <p><li><a href="#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?
- </p>
+ <li><a href="#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?<br />
</a></li>
- <p><li><a href="#quest18b">I get parse errors when I try to run Splint on code like #define
- MACROdebug(...) blahblah . Can I use variadic macros in Splint?</p>
+ <li><a href="#quest18b">I get parse errors when I try to run Splint on code like
+ #define MACROdebug(...) blahblah . Can I use variadic macros in Splint?<br />
</a></li>
- <p><li><a href="#quest20">I use realloc in my code. How can I get Splint in check this code more
- effectively?</p>
+ <li><a href="#quest20">I use realloc in my code. How can I get Splint in check this
+ code more effectively?<br />
</a></li>
- <p><li><a href="#quest21">I think I've found a bug in Splint. What should I do?</p>
+ <h4>Bugs</h4>
+ <li><a href="#quest21">I think I've found a bug in Splint. What should I do?<br />
</a></li>
- <p><li><a href="#quest22">Splint tells me that there is a bug and I should report it. What information
- should I send?</p>
+ <li><a href="#quest22">Splint tells me that there is a bug and I should report it.
+ What information should I send?<br />
</a></li>
- <p><li><a href="#quest23">My question isn't answered here. How can I get more information about
- Splint?</p>
+ <li><a href="#quest23">My question isn't answered here. How can I get more
+ information about Splint?<br />
</a></li>
</ol>
-
<h3>Questions and Answers</h3>
<ol>
-
- <li><p><a name="quest1">What is the difference between Splint and LCLint?</p>
- <p>Before 2002, Splint was known as LCLint. Splint 3.0 is the successor to LCLint
- 2.5.</p>
-
- <p><blockquote>LCLint was originally named for LCL, the Larch C Interface Language and lint, a
- well-known C program checking tool. Because our tool has diverged from LCL, and our
- focus now is on secure programming, it was renamed Splint. Splint's name has (at
- least) three interpretations: specifications lint, secure programming lint, and first
- aid for programmers. It's also easier to pronounce than LCLint.</p></blockquote>
- <li><p><a name="quest2">What is the Splint logo?</p>
- <p><blockquote>Thomas Jefferson's Serpentine Walls at the University of Virginia. The walls are
- one brick thick, but because of their design are both strong and aesthetic. Like a
- secure program, secure walls depend on sturdy bricks, solid construction, and elegant
- and principled design.</p></blockquote>
- <li><p><a name="quest3">Can I include Splint in my software distribution?</p>
- <p><blockquote>Yes. Splint is licensed under the GNU General Public License. You may redistribute
- it as you wish so long as credits and pointers to <a
- href="http://www.splint.org/">www.splint.org</a> are not changed or removed. Splint
- may be included in commercial distributions, and is included in several Linux and
- freeware CDs. If you redistribute Splint, please let us know by sending a message to
- <a href="mailto:splint@cs.virginia.edu">splint@cs.virginia.edu</a>.</p></blockquote>
- <li><p><a name="quest4">Can we use your software in our company? (We are not a GNU organization.)</p>
- <p><blockquote>Yes, splint is GPL-licensed. Anyone may use it. If you want to
- redistribute it, check the license for details or contact us.</p></blockquote>
- <li><p><a name="quest5">Does Splint handle C++?</p>
- <p><blockquote>No. Splint handles ISO C99 (and some gcc extensions if +gnuextensions is used). We
- don't have the resources (or the research justification) to build a C++ front end,
- but if you are interested in building a C++ front end the source code is available,
- and I will certainly be willing to help.</p></blockquote>
- <li><p><a name="quest6">I downloaded the Splint .tgz file but can't figure out how to extract it. There is
- no 'z' option on the tar on my system.</p>
- <p><blockquote>Check to see if there is GNU tar on your system, it is usually invoked by the
- command gtar or gnutar. GNU tar supports the -z option.</p>
- <p>You can also unzip the file then untar it. Do: gunzip filename.tar.gz to unzip
- then tar -xvf filename.tar</p></blockquote>
- <li><p><a name="quest7">I want to use Splint in win2000. How do I do that?</p>
- <p><blockquote>See <a href="http://www.splint.org/">www.splint.org</a> for information on
- Splint.</p>
- <p><a href="http://www.splint.org/win32.html">http://www.splint.org/win32.html</a>
- for Windows instructions.</p></blockquote>
- <li><p><a name="quest8">I have installed Splint for Windows 2000. Where should I put the ".splintrc"
- file?</p>
- <p><blockquote>For Win32, Splint looks for splint.rc instead of .splintrc due to the DOS filename problems. It will look first in the current directory, then in</p>
- <p>your home directory. See the Splint manual for more information.</p>
- </blockquote>
- <li><p><a name="quest9">Which compilers does Splint support?</p>
- <p><blockquote>It is independent from your compiler.</p></blockquote>
- <li><p><a name="quest10">How does Splint handle const?</p>
- <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>).</p></blockquote>
- <li><p><a name="quest11">Why do I get a Warning when multiplying different integer types? The C standard
- says this is ok. Why is this wrong?</p>
- <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.</p></blockquote>
- <li><p><a name="quest12">The C standard says that what I'm doing is okay. Why does Splint give me a
- warning?</p>
- <p><blockquote>See the previous question.</p></blockquote>
- <li><p><a name="quest13">Splint complains if I ignore the return value of scanf but not printf?</p>
- <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.</p>
- <p><blockquote>If you want stricter checking, use the flags +ansistrictlib, +posixstrictlib,
- +unixstrictlib to select the strict versions of these libraries.</p></blockquote>
- </blockquote>
- <li><p><a 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?</p>
+ <h4>General Questions About Splint</h4>
+ <li>
+ <p><a id="quest1" name="quest1">What is the difference between Splint and
+ LCLint?</a></p>
+ <p>Before 2002, Splint was known as LCLint. Splint 3.0 is the successor to LCLint
+ 2.5.</p>
+ <blockquote>
+ LCLint was originally named for LCL, the Larch C Interface Language and lint, a
+ well-known C program checking tool. Because our tool has diverged from LCL, and
+ our focus now is on secure programming, it was renamed Splint. Splint's name
+ has (at least) three interpretations: specifications lint, secure programming
+ lint, and first aid for programmers. It's also easier to pronounce than
+ LCLint.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest2" name="quest2">What is the Splint logo?</a></p>
+ <blockquote>
+ Thomas Jefferson's Serpentine Walls at the University of Virginia. The walls
+ are one brick thick, but because of their design are both strong and aesthetic.
+ Like a secure program, secure walls depend on sturdy bricks, solid
+ construction, and elegant and principled design.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest3" name="quest3">Can I include Splint in my software
+ distribution?</a></p>
+ <blockquote>
+ Yes. Splint is licensed under the GNU General Public License. You may
+ redistribute it as you wish so long as credits and pointers to <a
+ href="http://www.splint.org/">www.splint.org</a> are not changed or removed.
+ Splint may be included in commercial distributions, and is included in several
+ Linux and freeware CDs. If you redistribute Splint, please let us know by
+ sending a message to <a
+ href="mailto:splint@cs.virginia.edu">splint@cs.virginia.edu</a>.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest4" name="quest4">Can we use your software in our company? (We are
+ not a GNU organization.)</a></p>
+ <blockquote>
+ Yes, splint is GPL-licensed. Anyone may use it. If you want to redistribute it,
+ check the license for details or contact us.<br />
+ <br />
+ </blockquote>
+ </li>
- <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><p><a 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.</p>
- <p><blockquote>You can use -I to set the include path like you would with a compiler.</p></blockquote>
- <li><p><a 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 ?</p>
- <p><blockquote>Usually not, but Splint doesn't support all C99 extensions.</p></blockquote>
- <li><p><a name="quest16">I heard that Splint can generate some spurious errors ( not genuine errors). Is it
- correct ?</p>
- <p><blockquote>Yes, please see <a href="http://www.splint.org/">www.splint.org</a> for
- details.</p></blockquote>
- <li><p><a name="quest17">When I build Splint I get the following error:</p>
- <p><blockquote>Checking for...</p>
- <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>
- <p><blockquote>Those diffs look harmless. It is likely that your make is set up slightly
- differently than ours.</p></blockquote>
- <li><p><a 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?</p>
- <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.</p></blockquote>
- <li><p><a 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?</p>
- <p><blockquote>Sorry, Splint does not yet support variadic macros. We hope to fix this in a
- future release.</p></blockquote>
- <li><p><a name="quest20">I use realloc in my code. How can I get Splint in check this code more
- effectively?</p>
- <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.</p>
- <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><p><a name="quest21">I think I've found a bug in Splint. What should I do?</p>
- <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.</p></blockquote>
- <li><p><a name="quest22">Splint tells me that there is a bug and I should report it. What information
- should I send?</p>
- <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.</p>
- <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><p><a name="quest23">My question isn't answered here. How can I get more information about Splint?</p>
- <p><blockquote>First check the Splint manual and the mailing list archives.</p>
- <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>
-<table border="0" rules="none" bgcolor="#FFFFFF" width="95%" align=center cellpadding=0 cellspacing=0>
+ <li>
+ <p><a id="quest9" name="quest9">Which compilers does Splint support?</a></p>
+ <blockquote>
+ It is independent from your compiler.<br />
+ <br />
+ </blockquote>
+ </li>
-<tr valign=top>
-<td colspan=2 bgcolor="darkblue"></td>
-<tr valign=top>
-<td colspan=2 bgcolor="darkblue"></td>
-<tr valign=top>
-<td colspan=2 bgcolor="white"></td>
+ <li>
+ <p><a id="quest5" name="quest5">Does Splint handle C++?</a></p>
+ <blockquote>
+ No. Splint handles ISO C99 (and some gcc extensions if +gnuextensions is used).
+ We don't have the resources (or the research justification) to build a C++
+ front end, but if you are interested in building a C++ front end the source
+ code is available, and I will certainly be willing to help.<br />
+ <br />
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest6" name="quest6">I downloaded the Splint .tgz file but can't
+ figure out how to extract it. There is no 'z' option on the tar on my
+ system.</a></p>
+ <blockquote>
+ Check to see if there is GNU tar on your system, it is usually invoked by the
+ command gtar or gnutar. GNU tar supports the -z option.<br />
+ <br />
+
+ <p>You can also unzip the file then untar it. Do: gunzip filename.tar.gz to
+ unzip then tar -xvf filename.tar</p>
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest7" name="quest7">I want to use Splint in win2000. How do I do
+ that?</a></p>
+ <blockquote>
+ See <a href="http://www.splint.org/">www.splint.org</a> for information on
+ Splint.<br />
+ <br />
+
+ <p><a
+ href="http://www.splint.org/win32.html">http://www.splint.org/win32.html</a>
+ for Windows instructions.</p>
+ </blockquote>
+ </li>
+ <li>
+ <p><a id="quest8" name="quest8">I have installed Splint for Windows 2000. Where
+ should I put the ".splintrc" file?</a></p>
+ <blockquote>
+ For Win32, Splint looks for splint.rc instead of .splintrc due to the DOS
+ filename problems. It will look first in the current directory, then in<br />
+ <br />
+
+ <p>your home directory. See the Splint manual for more information.</p>
+ </blockquote>
+ </li>
+ <h4>Usage</h4>
-</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"-->
</body>
</html>
andersk / splint.git / commitdiff
