Error scanning C/C++ project

SonarQube Cloud
,
1

Hi, starting from 16.03.2026 all our C/C++ scans fail with the following scanner error:

Please contact SonarSource support providing the following file to help improving the analyzer:
...\\sonar-cfamily-reproducer.tar.xz

at com.sonar.cpp.plugin.CFamilySensor.logReproducerGeneration(CFamilySensor.java:1083)
at com.sonar.cpp.plugin.CFamilySensor.process(CFamilySensor.java:299)
at com.sonar.cpp.plugin.CFamilySensor.execute(CFamilySensor.java:217)
at org.sonar.scanner.sensor.AbstractSensorWrapper.analyse(AbstractSensorWrapper.java:68)
at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:75)
at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:51)
at org.sonar.scanner.scan.SpringModuleScanContainer.doAfterStart(SpringModuleScanContainer.java:74)
at org.sonar.scanner.spring.SpringComponentContainer.startComponents(SpringComponentContainer.java:208)
at org.sonar.scanner.spring.SpringComponentContainer.execute(SpringComponentContainer.java:187)
at org.sonar.scanner.scan.SpringProjectScanContainer.scan(SpringProjectScanContainer.java:219)
at org.sonar.scanner.scan.SpringProjectScanContainer.scanRecursively(SpringProjectScanContainer.java:214)
at org.sonar.scanner.scan.SpringProjectScanContainer.doAfterStart(SpringProjectScanContainer.java:182)
at org.sonar.scanner.spring.SpringComponentContainer.startComponents(SpringComponentContainer.java:208)
at org.sonar.scanner.spring.SpringComponentContainer.execute(SpringComponentContainer.java:187)
at org.sonar.scanner.bootstrap.SpringScannerContainer.doAfterStart(SpringScannerContainer.java:480)
at org.sonar.scanner.spring.SpringComponentContainer.startComponents(SpringComponentContainer.java:208)
at org.sonar.scanner.spring.SpringComponentContainer.execute(SpringComponentContainer.java:187)
at org.sonar.scanner.bootstrap.SpringGlobalContainer.doAfterStart(SpringGlobalContainer.java:150)
at org.sonar.scanner.spring.SpringComponentContainer.startComponents(SpringComponentContainer.java:208)
at org.sonar.scanner.spring.SpringComponentContainer.execute(SpringComponentContainer.java:187)
at org.sonar.scanner.bootstrap.ScannerMain.runScannerEngine(ScannerMain.java:143)
at org.sonar.scanner.bootstrap.ScannerMain.run(ScannerMain.java:58)
at org.sonar.scanner.bootstrap.ScannerMain.main(ScannerMain.java:42)

Please assist ASSAP.

2

Hi,

Can you help me understand what 16.03 is the version number of? I don’t know how to correlate that, off-hand, to our products.

 
Thx,
Ann

3

That is not a number - it a date (3/16/2026) :).
Without any changes from our side sonar scanner fails: C++ analyzer is crashing with exit code 139 (SIGSEGV/segmentation fault). We use sonarcloud.io and every time download wrapper from https://sonarcloud.io/static/cpp/build-wrapper-linux-x86.zip

4

Hi @siarheimalyshau,

Welcome to the community!

I take it you work with the OP?

I’m still not clear on what version you’re running. We version both SonarQube Server and SonarQube community build, with the year, but not like that. The current version of SonarQube Server is 2026.1, and the version we release at the end of the month will be 2026.2. The current version of SonarQube Community Build is 26.3. And it was released on March 3, 2026. So even as a date, that still doesn’t correlate for me.

Can you tell me what it says in the page footer?

 
Thx,
Ann

5

Hi Ann,
We use Paid “Team” SonarCloud version and our CI pipeline relies on it.
Starting from 16 March 2026 C++ scans fail, with the error provided.

Could you please assist with the problem?

image
image840Ă—294 32 KB

6

Hi,

Yes, you filed this in the SonarQube Cloud category. Correctly, it seems. And many people don’t choose the right category. So when you provide a version number, I have to ask questions.

Can you upload the reproducer?

 
Thx,
Ann

7

Yes, please describe a way how we can do it securely as it contains proprietary software sources.

10

Hi @andreisamuta,

I started a private thread to collect some information.

Thank you,
Michael

1 Like
11

The issue was identified, a temporary workaround was shared with the user, and an internal ticket was created to fix the problem in the next version.

Thanks @andreisamuta for sharing the reproducer with us.

Best regards,
Michael

1 Like