Code Analysis (static analysis) issues display in a view within Code Sight.
The view that displays depends on which IDE you are running:
- In Eclipse and Visual Studio, the list of issues appears in the Code Analysis view, as in previous versions of Code Sight.
- In JetBrains IDEs, including IntelliJ, and in VS Code, the list of issues appears in Local View.
In Eclipse, remote issues continue to appear in the Code Analysis view while Remote mode is active.
Scan mode
In Eclipse, IntelliJ (and its JetBrains variants), and Visual Studio, buttons let you choose the scan mode.
In VS Code, choose the scan mode by clicking the Mode entry at the top of the LOCAL VIEW, and then using the drop-down menu that appears.
Use the buttons or the menu to choose between auto-scan or manual scan mode.
- Auto (not available in Eclipse)
- Launches Rapid Scan Static for an individual file whenever you open or save that file.
- Manual
- Launches scans for individual files or for the entire source project. A manual scan can be a Coverity scan as well as a Rapid Scan.
- Remote (Eclipse only)
-
Lists remote issues; that is, issues found by the Coverity server, which can be either
Coverity Connect or Coverity on Polaris.
Attention: For JetBrains IDEs (including IntelliJ), Visual Studio, and VS Code, issues detected remotely by a Coverity server (either Coverity Connect or Coverity on Polaris) now appear in the Team View. There is no longer a Remote scan mode in IDEs other than Eclipse.
In Eclipse, Polaris issues now appear in Team View.
Controls for manual scanning
These controls are disabled when auto-scan is active. They give you a choice of which static-analysis engine to run:
- Coverity Analysis performs comprehensive and detailed scanning that can be synchronized with a server.
- Rapid Scan Static performs rapid scanning locally.
Use the drop-down list to choose which scan engine to use, and the scope of the scan.
In Eclipse and Visual Studio, the drop-down list appears just before the SCAN icon.
IntelliJ and VS Code now use Local View and scan configurations instead: See Local View and scan configurations (IntelliJ and VS Code).
After choosing which engine to run, and the scope of the scan, click the SCAN icon or label to launch the scan.
In Eclipse, IntelliJ, and Visual Studio:
-
Click the SCAN icon or label to launch a scan of the type you chose.
-
While a scan is running, the SCAN icon changes to a red square.
You can click the red icon to cancel the scan.
In VS Code:
-
Click the SCAN icon to launch a scan of the type you chose.
-
While a scan is running, the SCAN icon changes to an icon with an X.
You can click the X icon to cancel the scan.
The Issues list
Lists Code Analysis issues that Code Sight has found.
In Eclipse, IntelliJ, and Visual Studio (but not in VS Code), the list of issues is organized into the following columns (VS Code does display severities):
- Severity
-
Icons in this column indicate the severity level of the issue:
Low
Medium
High
Critical
- Issue Type
- A brief description of the issue that was found
- Location
- The name of the file and the line number where the issue was found.
- First Detected
- Indicates how long ago the issue was first detected.
Issue Details
Code Sight displays issue details when you click to highlight an issue in the Issues list. The Issue Details panel also gives you access to a view titled Contributing Details.
Please see Issue Details: Coverity (SAST), Contributing Details: Coverity (SAST), and Issue Details: Rapid Scan Static.
Filter controls
In Eclipse and Visual Studio, the Filter icons control which Code Analysis issues appear on the list in this view.
-
Show issues from only the active file
-
Show issues from all scanned files
-
Show all dismissed issues