C/C++ Path Analysis errors

In this topic:

If your organization complies with Functional Safety standards, then these errors are likely of interest to you. Functional Safety organizations have processes in place to review and analyze these errors. Otherwise, you can ignore them.

If the engine is unable to analyze a particular function, a message will be added to the function information log, which is found in the output tables directory. These messages are explained below.

Time-out

Message Explanation
Path Analysis: Info: Function 'x' was skipped. Status code 501 (timeout) The function took too long to analyze.

Complexity

Message Explanation
Path Analysis: Info: Function 'x' was skipped. Status code 601 This means that Klocwork's interprocedural checkers will not be run on this function, but Klocwork will still run intra-procedural checkers on the function. If you see this message, you need to reduce the size and complexity of the function.
Path Analysis: Info: Function 'x' was skipped. Status code 602
Path Analysis: Info: Function 'x' was skipped. Status code 603
Path Analysis: Info: Function 'x' was skipped. Status code 604
Path Analysis: Info: Function 'x' was skipped. Status code 701 These status codes indicate that the function was passed to the classic engine for analysis. They are meant for internal use only and can be ignored.
Path Analysis: Info: Function 'x' was skipped. Status code 702
Path Analysis: Info: Function 'x' was skipped. Status code 703
Path Analysis: Info: Function 'x' was skipped. Status code 704

See also

Creating C/C++ Path checkers