From 96c3605a2b09b978fb2112da1938aeefe73c7e50 Mon Sep 17 00:00:00 2001 From: drl7x Date: Mon, 21 Apr 2003 04:13:02 +0000 Subject: [PATCH] Indexed faq.html --- doc/html/faq.html | 233 ++++++++++++++++++++++++---------------------- 1 file changed, 120 insertions(+), 113 deletions(-) diff --git a/doc/html/faq.html b/doc/html/faq.html index 734c08e..dd1561c 100644 --- a/doc/html/faq.html +++ b/doc/html/faq.html @@ -14,7 +14,7 @@

Index

    -

    General Questions About Splint

    +

    General Questions About Splint

  1. What is the difference between Splint and LCLint?
    @@ -25,11 +25,13 @@
  2. Can we use your software in our company? (We are not a GNU organization.)
    +
  3. +
  4. Which compilers does Splint support?
  5. Does Splint handle C++?
  6. -

    Installation

    +

    Installation

  7. 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.
  8. @@ -38,60 +40,61 @@
  9. I have installed Splint for Windows 2000. Where should I put the ".splintrc" file?
  10. -

    Usage

    -
  11. Which compilers does Splint support?
    +
  12. When I build Splint I get the following errors.... Should I be worried?
  13. -
  14. How does Splint handle const?
    +
  15. 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?
  16. -
  17. Why do I get a warning when multiplying different integer - types? The C standard says this is ok. Why is this wrong?
    +

    Usage

    +
  18. 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 ?
  19. -
  20. The C standard says that what I'm doing is okay. Why does - Splint give me a warning?
    +
  21. I heard that Splint can generate some spurious errors ( not + genuine errors). Is it correct ?
  22. -
  23. Splint complains if I ignore the return value of scanf but - not printf?
    +
  24. How does Splint handle const?
  25. -
  26. I develop code on an embedded system with a compiler that +
  27. 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?
  28. How can I get Splint to recognize directory trees and local source include directories?
  29. -
  30. 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 ?
    + +
  31. I use realloc in my code. How can I get Splint in check this + code more effectively?
  32. -
  33. I heard that Splint can generate some spurious errors ( not - genuine errors). Is it correct ?
    + +

    Warnings and Errors

    +
  34. Why do I get a warning when multiplying different integer + types? The C standard says this is ok. Why is this wrong?
  35. -
  36. When I build Splint I get the following errors.... Should I - be worried?
    +
  37. The C standard says that what I'm doing is okay. Why does + Splint give me a warning?
  38. -
  39. 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?
    +
  40. Splint complains if I ignore the return value of scanf but + not printf?
  41. I get parse errors when I try to run Splint on code like #define MACROdebug(...) blahblah . Can I use variadic macros in Splint?
  42. -
  43. I use realloc in my code. How can I get Splint in check this - code more effectively?
    -
  44. -

    Bugs

    +

    Bugs

  45. I think I've found a bug in Splint. What should I do?
  46. Splint tells me that there is a bug and I should report it. What information should I send?
  47. +

    Additional Information

  48. My question isn't answered here. How can I get more information about Splint?

Questions and Answers

    -

    General Questions About Splint

    +

    General Questions About Splint

  1. What is the difference between Splint and LCLint?

    @@ -159,6 +162,7 @@
  2. +

    Installation

  3. 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 @@ -196,53 +200,79 @@

    your home directory. See the Splint manual for more information.

  4. -

    Usage

    - +
  5. -

    How does Splint handle const?

    +

    When I build Splint I get the following + error:

    - Splint doesn't interpret const (at all). See the manual section on modifies - checking (http://www.splint.org/manual/html/sec7.html).
    + Checking for...
    +
    + +

    Checking manual...

    +

    cmx > / Checking tests2.2...

    +

    Checking tests2.4...

    +

    Checking tests2.5...

    +

    Checking db1...

    +

    0a1,2

    +

    > /cmx/tools/make -e clean

    +

    > /cmx/tools/make -e check

    +

    *** FAIL ***

    +

    Checking db2...

    +

    0a1,/tools/make -e clean

    +

    > /cmx/tools/make -e check

    +

    *** FAIL ***

    +

    Checking db3...

    +
    +

    Should I be worried?

    +
    + Those diffs look harmless. It is likely that your make is set up slightly + differently than ours.

  6. -

    Why do I get a Warning when multiplying - different integer types? The C standard says this is ok. Why is this - wrong?

    +

    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?

    - 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.
    + 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.

  7. -
  8. -

    The C standard says that what I'm doing is - okay. Why does Splint give me a warning?

    +

    Usage

    +
  9. +

    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 ?

    - See the previous question.
    + Usually not, but Splint doesn't support all C99 extensions.

  10. -

    Splint complains if I ignore the return value - of scanf but not printf?

    +

    I heard that Splint can generate some spurious + errors ( not genuine errors). Is it correct ?

    - 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.
    + Yes, please see www.splint.org for + details.

    - -
    - If you want stricter checking, use the flags +ansistrictlib, +posixstrictlib, - +unixstrictlib to select the strict versions of these libraries.
    -
    -
  11. +

    How does Splint handle const?

    +
    + Splint doesn't interpret const (at all). See the manual section on modifies + checking (http://www.splint.org/manual/html/sec7.html).
    +
    +
    +
  12. +
  13. 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 @@ -264,69 +294,58 @@

  14. -
  15. -

    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 ?

    +
  16. +

    I use realloc in my code. How can I get Splint + in check this code more effectively?

    - Usually not, but Splint doesn't support all C99 extensions.
    + 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.

    + +

    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:

    +

    http://www.splint.org/documentation/realloc.htm

  17. +

    Warnings and Errors

  18. -

    I heard that Splint can generate some spurious - errors ( not genuine errors). Is it correct ?

    +

    Why do I get a Warning when multiplying + different integer types? The C standard says this is ok. Why is this + wrong?

    - Yes, please see www.splint.org for - details.
    + 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.

  19. -

    When I build Splint I get the following - error:

    -
    - Checking for...
    -
    - -

    Checking manual...

    -

    cmx > / Checking tests2.2...

    -

    Checking tests2.4...

    -

    Checking tests2.5...

    -

    Checking db1...

    -

    0a1,2

    -

    > /cmx/tools/make -e clean

    -

    > /cmx/tools/make -e check

    -

    *** FAIL ***

    -

    Checking db2...

    -

    0a1,/tools/make -e clean

    -

    > /cmx/tools/make -e check

    -

    *** FAIL ***

    -

    Checking db3...

    -
    -

    Should I be worried?

    +

    The C standard says that what I'm doing is + okay. Why does Splint give me a warning?

    - Those diffs look harmless. It is likely that your make is set up slightly - differently than ours.
    + See the previous question.

  20. -

    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?

    +

    Splint complains if I ignore the return value + of scanf but not printf?

    - 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.
    + 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.

    + +
    + If you want stricter checking, use the flags +ansistrictlib, +posixstrictlib, + +unixstrictlib to select the strict versions of these libraries.
    +
    +
  21. -
  22. -

    I get parse errors when I try to run Splint +

  23. I get parse errors when I try to run Splint on code like #define MACROdebug(...) blahblah . Can I use variadic macros in Splint?

    @@ -335,21 +354,8 @@
  24. -
  25. -

    I use realloc in my code. How can I get Splint - in check this code more effectively?

    -
    - 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.
    -
    - -

    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:

    -

    http://www.splint.org/documentation/realloc.htm

    -
    -
  26. + +

    Bugs

  27. I think I've found a bug in Splint. What should I do?

    @@ -373,6 +379,7 @@ may be able to at least to offer you advice on working around the problem.

  28. +

    Additional Information

  29. My question isn't answered here. How can I get more information about Splint?

    -- 2.45.1