SonarQube does not highlight all c-code issues by rule "Variables should be initialized before use"

Template for a good bug report, formatted with Markdown:

  • versions used (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarQube Enterprise Edition Version 8.9 (build 43852)
  • error observed (wrap logs/code around triple quote ``` for proper formatting)
our issue code snippet can be in following flow:
int function(int flag, int b) {
  int a;
  if (flag) {
    a = b;
  return a; // Noncompliant - "a" has not been initialized in all paths

  • steps to reproduce
    in fact, we found 4 c-language code snippets with above issue, 3 were detected by SonarQube, while 1 was not detected.

  • potential workaround

P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour

“You are not permitted to view the requested resource.” when I change this issue category to Fault.
this is a rule-related bug.

Hello @rubin,
Thanks for your report.

I checked locally, and our analyzer seems to detect the issue you are referring to. So it must be something in the environment or other part of your code that leads to this false-negative. To help investigate, please provide the reproducer file that helps us reproduce the issue on our side. To generate the reproducer file:

  • Add the reproducer option to the scanner configuration:
    sonar.cfamily.reproducer= "Full path to the .cpp file that has or include the file that has the false-positive"
  • Re-run the scanner to generate a file named sonar-cfamily.reproducer in the project folder.
  • Please share this file. If you think this file contains private information, you can send it privately.


we re-run sonar-scanner, which told:

ERROR: Requesting reproducer for: /full_path/xxx_init.c
INFO: [pool-1-thread-1] /full_path/xxx_init.c
INFO: PCH: unique=0 use=0 (forceInclude=0,throughHeader=0,firstInclude=0) out of 1 (forceInclude=0,throughHeader=0)
INFO: SE: 1 out of 1