Versions Compared

Old Version 1

changes.mady.by.user Robert Andelin

Saved on

compared with

New Version Current

changes.mady.by.user Izabela Jarosz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DTPDEVEL and version 2025.2

...

Scroll Table Layout
widths30%,70%

Incremental analysis

Enable Enable incremental analysis to run flow analysis in incremental mode. Incremental mode reduces the time required to run analysis during nightly runs on a single code base that changes from day to day.

Enable Compact incremental caches and specify how frequently unnecessary data that may have been cached is removed.

This option is available for C++test only.  

Depth of analysisChoose the depth of flow analysis. A deeper setting results in more findings but may results in slower analysis and greater memory consumption.
Strategy for timeouts

Configure the timeout settings for flow analysis.

Enable time and specify how many seconds flow analysis should wait before timing out when analyzing a single point in the code.

Enable instructions and specify the maximum number of flow analysis instructions allowed when analyzing a single point in the code.

Enable off to disable timeouts.

Enables swapping of analysis data to diskEnable this option to allow the flow analysis tool to write the data necessary for analysis to disk. This prevents flow analysis from consuming all available memory when analyzing a large project in which the data represents a semantic model of the analyzed source code.

Verbosity Settings

Expand this section to access options related to how much detail is included in the report.

...

Scroll Table Layout
widths30%,70%

Do not report violations when cause cannot be shown

Enable this option if you want to exclude violations that lack a cause from being reported. Complete paths from the cause to the point of violation are reported if this option is enabled, but violation causes are not reported for paths that have multiple causes.

Do not report more than one violation per pointEnable this option to restrict the number reported violations when the cause or point of violation is shared.
Do Not report violations whose paths pass via inline assembly codeEnable this option to report violations whose paths are passed with inline assembly code instructions. C/C++test only.
Report problems with building analysis dataEnable this option to report a set up problem if flow analysis encounters a problem while building analysis data.

Null-Checking Methods Settings

...

Scroll Table Layout
orientationdefault
sortDirectionASC
repeatTableHeadersdefault
widths30%,70%
sortByColumn1
sortEnabledfalse
cellHighlightingtrue

External files to analyzeSpecifies absolute paths to additional header files to be analyzed by Flow Analysis. Use wildcards to specify the pattern.
External functions to analyze

Specifies additional functions to be analyzed by Flow Analysis. Complete the table with the following information:

  • Enabled: specifies whether the function should be considered during analysis
  • Fully-qualified type name or namespace (wildcard): the fully qualified name of the type or namespace where the function is declared. Use '*' if you want to describe a function declared in any type or namespace, or a global function declared outside of any type.
  • Function name (wildcard): the name of the function. '*' can be used to denote any number of any symbols.
  • Number of parameters: specifies the number of function's parameters. '-1' can be used to denote any number of parameters.
  • + definitions in subclasses: a checkbox that indicates whether the definitions (of functions with the given name) in subclasses should be included as well. Note that this applies to both instance and static functions.

Compiler-Specific Settings 

...