SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C

C static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C code

  • All rules 420
  • Vulnerability14
  • Bug111
  • Security Hotspot19
  • Code Smell276

  • Quick Fix 27
Filtered: 25 rules found
bad-practice
    Impact
      Clean code attribute
        1. Pointer and reference parameters should be "const" if the corresponding object is not modified

           Code Smell
        2. Reserved identifiers should not be defined or declared

           Code Smell
        3. Only standard forms of the "defined" directive should be used

           Code Smell
        4. Function-like macros should not be used

           Code Smell
        5. Recursion should not be used

           Code Smell
        6. "continue" should not be used

           Code Smell
        7. Bitwise operators should not be applied to signed operands

           Bug
        8. Functions should be declared explicitly

           Code Smell
        9. Names of well-known C standard library macros and functions should not be used as identifiers

           Code Smell
        10. Macros should not be used as replacements for "typedef" and "using"

           Code Smell
        11. Size of bit fields should not exceed the size of their types

           Code Smell
        12. Pointer and reference local variables should be "const" if the corresponding object is not modified

           Code Smell
        13. Argument of "printf" should be a format string

           Code Smell
        14. Loops with at most one iteration should be refactored

           Bug
        15. "if" statements should be preferred over "switch" when simpler

           Code Smell
        16. Track uses of "NOSONAR" comments

           Code Smell
        17. Deprecated attributes should include explanations

           Code Smell
        18. The literal value zero shall be the only value assigned to "errno"

           Code Smell
        19. The operands of "bitwise operators" and "shift operators" shall be appropriate

           Bug
        20. "Dynamic memory" should not be used

           Code Smell
        21. Precautions shall be taken in order to prevent the contents of a "header file" being included more than once

           Code Smell
        22. All "#else", "#elif" and "#endif" preprocessor directives shall reside in the same file as the "#if", "#ifdef" or "#ifndef" directive to which they are related

           Code Smell
        23. Functions shall not call themselves, either directly or indirectly

           Code Smell
        24. The target type of a pointer or "lvalue" reference parameter should be const-qualified appropriately

           Code Smell
        25. "Trigraph-like sequences" should not be used

           Code Smell

        Functions shall not call themselves, either directly or indirectly

        intentionality - logical
        maintainability
        Code Smell
        • bad-practice
        • pitfall
        • misra-c++2023
        • misra-required

        Why is this an issue?

        More Info

        This rule is part of MISRA C++:2023.

        Usage of this content is governed by Sonar’s terms and conditions. Redistribution is prohibited.

        Rule 8.2.10 - Functions shall not call themselves, either directly or indirectly

        Category: Required

        Analysis: Undecidable,System

        Rationale

        Recursion carries with it the danger of exceeding available stack space, which can lead to a serious failure. Unless recursion is very tightly controlled, it is not possible to determine before execution what the worst-case stack usage could be.

        Note: any deviation used to justify non-compliance with this rule will need to explain how stack usage is to be controlled.

        Exception

        A constexpr function that is only called within a core constant expression may be recursive.

        Example

        int32_t fn( int32_t x )
        {
          if ( x > 0 )
          {
            x = x * fn( x - 1 );              // Non-compliant
          }
        
          return x;
        }
        
        // File1.cpp
        int32_t fn_3( int32_t x );
        
        int32_t fn_2( int32_t x )
        {
          if ( x > 0 )
          {
            x = x * fn_3( x - 1 );            // Non-compliant
          }
        
          return x;
        }
        
        // File2.cpp
        int32_t fn_2( int32_t x );
        
        int32_t fn_3( int32_t x )
        {
          if ( x > 0 )
          {
            x = x * fn_2( x - 1 );            // Non-compliant
          }
        
          return x;
        }
        

        In the following, the recursion within fn_4 satisfies the requirements of the exception as it is only called from within a core constant expression.

        constexpr int32_t fn_4( int32_t x )
        {
          if ( x > 0 )
          {
            x = x * fn_4( x - 1 );            // Compliant by exception
          }
        
          return x;
        }
        
        constexpr int32_t n = fn_4( 6 );      // Core constant expression
        
        
        constexpr int32_t fn_5( int32_t x )
        {
          if ( x > 0 )
          {
            x = x * fn_5( x - 1 );            // Non-compliant
          }
        
          return x;
        }
        
        int32_t n = fn_5( 6 );                // Not a core constant expression
        
        
        template< class T >
        auto Sum( T t )
        {
          return t;
        }
        
        template< class T, class ... Vals >
        auto Sum( T t, Vals ... vals )
        {
          return t + Sum( vals ... );         // Compliant - calls a different overload
        }
        

        Copyright The MISRA Consortium Limited © 2023

          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use