Libraries used (-library)

The analysis uses smart stubs only for functions from the C Standard Library.

The analysis uses smart stubs for AUTOSAR RTE API functions even if their implementations are available.

The option also triggers AUTOSAR-specific checks on function arguments. For more information, see the corresponding checkers:

The analysis uses smart stubs for methods from C++ Standard Library containers even if their implementations are available.

The containers whose methods are stubbed include std::map, std::unordered_map, std::deque, std::vector, std::set, std::unordered_set, and std::list. If you use this option and your code contains C++ container methods, the analysis log contains a message:

n methods stubbed for better performance

Note that unlike functions from the C Standard Library, the stubs of C++ container methods are not used to check for domain errors and other error conditions. The methods are stubbed to avoid the unnecessary performance costs from analyzing their implementation. As a result, if you invoke a C++ container method with incorrect arguments, you do not see errors that refer to the incorrect invocation. But in some cases, you might see other errors that indirectly follow from the incorrect invocation. For instance, if you invoke the std::stack::top() method on an empty stack, you see a Non-initialized variable error even though the stack itself is initialized.

This option has effect only on a Code Prover analysis. A Bug Finder analysis discards implementations of C++ container methods immediately after compilation and does not require the smart stubbing.

The analysis uses smart stubs for test-specific macros and classes from the Polyspace^® Test™ xUnit API. This option is automatically added if you run static analysis on a test in the Polyspace Platform user interface. For more information, see Check for Bugs and Run-Time Errors in C/C++ Tests and Functions Under Test (Polyspace Test).