SonarScanner exception during analysis

  • ALM used: GitLab

  • CI system used: Gitlab CI/CD

  • Scanner command used when applicable: sonar-scanner“” -Dsonar.token=“*”

  • Languages of the repository: C++

  • Error observed:

INFO: [pool-4-thread-1] /eps/firmware/bootloader/src/bootloader.cpp
INFO: Reached stage: symbolic execution
INFO: Requesting reproducer for: /eps/firmware/bootloader/src/bootloader.cpp
ERROR: Exception in thread pool-4-thread-1
com.sonar.cpp.analyzer.Analyzer$AnalyzerException: Exit code != 0: /eps/firmware/bootloader/src/bootloader.cpp
        at com.sonar.cpp.analyzer.AnalysisHandler.acceptResult(
        at com.sonar.cpp.analyzer.Subprocess.execute(
        at com.sonar.cpp.plugin.CFamilySensor.lambda$process$19(
        at com.sonar.cpp.analyzer.AnalysisExecutor.lambda$submit$0(
        at java.base/java.util.concurrent.Executors$ Source)
        at java.base/ Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$ Source)
        at java.base/ Source)

An error occurred while analyzing the following compilation unit:

After changing CFamily plugin version from to SonarScanner started throwing exception despite no change in code. Only workaround for no is to exclude file that throws exception.

Let me know how to provide

Hi @pszemoc,

I sent you a PM where you can share the reproducer.


Hi @pszemoc,

Thanks for the report!

This was fixed in 6.39 in this ticket: [CPP-3889] - Jira. The new release should be available in a week. Until then excluding the file is the best approach.

Sorry for the inconvenience.


1 Like

Thanks a lot!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.