ⓘ Information

The content on this page has moved: https://docs.sonarsource.com/sonarlint/visual-studio/troubleshooting/#troubleshooting-c-or-c-analysis

The SonarLint documentation has moved! Please visit https://docs.sonarsource.com/sonarlint/visual-studio/ to have a look at the new documentation website. We’ve improved the documentation as a whole, integrated the four SonarLint IDE extension docs together, and moved everything under the sonarsource.com domain to share a home with the SonarQube docs (SonarCloud to come in Q3 of 2023).

These GitHub wikis will no longer be updated after October 1st, 2023 but no worries, we’ll keep them around a while for those running previous versions of SonarLint for Visual Studio.

Overview

Starting with version 4.21, it is possible to create a "reproducer" file for C/C++ analysis. A reproducer file contains diagnostic information to help the developers at SonarSource investigate problems that occur during C/C++ analysis.

Note: Starting with version 4.27, a second "reproducer" file is created with additional debug information.

If you encounter a problem with C/C++ analysis, please contact us in the community forum and include the reproducer file(s).

Creating a reproducer file for the Active Document

To create a reproducer:

• open the C/C++ file that is not being analysed correctly
• open Visual Studio's Command Window, found under View -> Other Windows -> Command Window.
• type in the command window "Analyze.SonarLint.CFamily.CreateReproducer":

You can then view the location of the created reproducer file(s) in the SonarLint Output pane:

Reproducer file in SonarLint 4.21-4.26

Reproducer files in SonarLint 4.27

Notes:

• the reproducer file(s) are regenerated each time the command is invoked. Invoking the command will overwrite the previous reproducer file(s).
• running the reproducer will only produce the reproducer file(s). It will not report any issues for the active C/C++ file.