Our website uses cookies to enhance your browsing experience.
Accept
to the top
>
>
View and mark up analysis results
menu mobile close menu
Analyzing projects
Additional information
toggle menu Contents

View and mark up analysis results

Aug 26 2026

Report

Source code pane

The central pane has separate tabs for displaying the source code and rule documentation. When a warning is selected, the view automatically navigates to the corresponding line of code.

Click the grid icon to display all hidden tabs.

Note. You can edit and save source code files only in the Atlas Viewer edition, and only before the source code is packaged into a .pvsmap report.

Warning view pane

Pane overview

The bottom pane contains filters for navigating through analyzer warnings:

Key elements of the Warning view pane:

  • Current report name (available only in the Atlas Viewer edition)
  • Save menu
  • Warning toggle buttons
  • Severity level filter
  • Category filter
  • Status filter
  • Column filter
  • Warning main window.

The following columns provide information about warnings:

  • Favorites marks a warning as important for further analysis. Available only in the Atlas Viewer edition.
  • Code displays the rule identifier. Helps sort warnings by code and quickly find the corresponding documentation. Clicking the Code opens a documentation page with a rule description and examples of how to fix the issue.
  • Message displays a general description of the issue detected by the analyzer. Provides a basic understanding of the issue with no need to consult the documentation.
  • File specifies the name of the source file that contains the warning. The full file path or only the file name can be displayed.
  • Line specifies the code line in the source file that contains the warning.

Additional columns:

  • Number. The number of the warning in the report.
  • Project. The name of the project containing the file with the warning.
  • Status. The status assigned to the warning.
  • Severity. The severity assigned to the warning.
  • Date. The date of the last change to the line indicated by the analyzer.
  • Author. The author of the most recent change to the line indicated by the analyzer.
  • Revision. The hash or revision number of the line identified by the analyzer.

Warning context menu

The context menu is available for each warning:

The context menu enables the following actions:

  • Show full paths: The File column displays the full path to the file.
  • Show columns: Enables or disables the display of additional table columns.
  • Mark selected warnings by status: Assigns the same status to multiple selected warnings.
  • Mark all warnings from...: Assigns a single status to warnings under the selected path.
  • Copy selected warnings: Generates text from the diagnostic code, warning, file name, and line number.
  • Add selected warnings to favorites: Available only in the Atlas Viewer edition.

Warning category filter pane

One of the main filters. Allows focusing on specific analysis categories relevant to the project. It will not display all analyzer findings at once.

List of categories:

  • General — the main set of PVS-Studio diagnostic rules.
  • Optimization — diagnostic rules for identifying code optimization opportunities.
  • Security Related Issues —diagnostic rules for identifying potential security issues.
  • CWE — diagnostic rules for identifying potential vulnerabilities in accordance with the Common Weakness Enumeration (CWE).
  • SEI CERT — diagnostic rules for identifying potential vulnerabilities in accordance with the SEI CERT Coding Standards.
  • OWASP ASVS — diagnostic rules for identifying security issues in accordance with the OWASP Application Security Verification Standard (ASVS).
  • 64-bit Errors — diagnostic rules for identifying errors in C or C++ code ported to 64-bit systems.
  • MISRA C 2012 — diagnostic rules for verifying compliance with the MISRA C 2012 standard.
  • MISRA C 2023 — diagnostic rules for verifying compliance with the MISRA C 2023 standard.
  • MISRA C++ 2008 — diagnostic rules for verifying compliance with the MISRA C++ 2008 standard.
  • MISRA C++ 2023 — diagnostic rules for verifying compliance with the MISRA C++ 2023 standard.
  • Customer Specific — diagnostic rules developed for specific customer requests and not included in the main categories.
  • Analyzer Fails — diagnostic rules displaying analyzer errors.

Diagnostic rules that apply to multiple categories remain in the table when these categories are selected. Their warnings will not be duplicated, so marking one category increases the markup percentage of the other.

The Statistics section shows the breakdown of all warnings in the analyzer report by category, including their percentage share.

Warning column filter pane

The column filter is available on a collapsible pane that can be displayed by the column filter button. Text input fields for filtering warnings are only available for enabled columns.

Warning severity and status filter pane

The severity and status filters are used to filter warnings based on previously applied markup. The types of markup are described in the Markup Panel section.

Markup Panel

The Markup Panel on the right is used to classify warnings and assign statuses and comments to distinguish real defects from false positives.

Markup statuses:

  • New. A new analyzer warning. This status can only be assigned by the platform.
  • Resolved. A warning that is no longer reported in the source code. This status can only be assigned by the platform.
  • Reopened. A warning that was previously Resolved but has reappeared in the code. This status can be assigned either by the platform or manually. When assigned manually, it serves as an alternative to New, which cannot be assigned manually.
  • Confirmed. A confirmed issue that requires a code fix.
  • Conflict. A special status assigned by the platform when merging multiple reports with analysis results. To resolve the conflict, manually assign another status to the warning.
  • False Positive. A false alarm from the analyzer.
  • Wontfix. A warning is technically valid, but this markup shows that the issue is not going to be fixed.

Severity levels:

  • Blocker
  • Critical
  • Major
  • Minor
  • Info.

By default, all warnings are assigned a default severity level. It can be changed either while marking up an existing report or by assigning a custom severity level to a warning code in the quality profile. When merging multiple reports with annotated analysis results, if the severity levels differ, the more severe level is assigned automatically. When markup is enabled, it allows users to add comments.

Statistics

The Statistics section displays information about the analysis results and the markup of warnings in the currently open report:

The table contains summary data grouped by diagnostic rule category and markup status. A warning may belong to multiple categories if the analyzer supports it. When such a warning is marked up, the markup percentage changes in all related categories.

This section generates a final markup report in HTML format that can be exported to PDF.