Some PC-lint errors are fatal (or close to fatal) in nature, and require the PC-lint configuration to be corrected before analysis can resume.
The ones you are most likely to see are:
Fatal Error 307: Can’t open indirect file
This error indicates that PC-lint was unable to locate a .lnt file on its search path. Check that the file exists in the correct location and that PC-lint has a –i directive locating its folder in either the std.lnt file or the generated project.lnt file.
Fatal Error 314: Previously used .lnt file
Each .lnt file can only be used once in the command line - directly or by inference. If you see this error, check your configuration files and command line for repeated .lnt files.
Fatal Error 322/Error 7: Unable to open include file
If an include file cannot be found you will receive fatal error 322 and analysis will abort, unless error 322 has been suppressed - in which case error 7 will be raised instead and analysis will continue. In either case, check the include paths (–i directives) and pre-processor symbol definitions (–D and –U directives) – particularly in the project.lnt files which Visual Lint generates from your project files.
If a –i directive for the folder containing the header file cannot be located and you believe it should have been automatically generated (or a generated project.lnt file appears incomplete in some other way), please contact us - it could be that your project or environment represents a variant we have not yet encountered.
Error 91: Line exceeds Integer characters (use +linebuf)
Some versions of PC-lint have a fixed line buffer of 620 characters. If you see this message, add a +linebuf directive (which doubles the size of the buffer) to the command line via the "Command Line" Options page and try again. Repeat the process until the error disappears.
Fatal Error 303: String too long (try +macros)
This is similar to error 91, but this time in macro definitions. Add +macrobuf directives until it goes away.