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: 27 rules found
unpredictable
    Impact
      Clean code attribute
        1. Arguments evaluation order should not be relied on

           Bug
        2. Keywords shall not be used as macros identifiers

           Code Smell
        3. Dereferenced null pointers should not be bound to references

           Code Smell
        4. Header guards should be followed by a matching "#define" macro

           Code Smell
        5. "memcmp" should only be called with pointers to trivially copyable types with no padding

           Bug
        6. Stack allocated memory and non-owned memory should not be freed

           Bug
        7. The "<stdlib.h>" functions "bsearch" and "qsort" should not be used

           Bug
        8. Floating-point arithmetic should be used appropriately

           Bug
        9. There shall be no occurrence of "undefined" or "critical unspecified behaviour"

           Bug
        10. An "object pointer type" shall not be cast to an integral type other than "std::uintptr_t" or "std::intptr_t"

           Code Smell
        11. The pointers returned by the C++ Standard Library functions "localeconv", "getenv", "setlocale" or "strerror" must only be used as if they have pointer to const-qualified type

           Bug
        12. Reads and writes on the same file stream shall be separated by a positioning operation

           Bug
        13. Local variables shall not have static storage duration

           Code Smell
        14. The pointer returned by the C++ Standard Library functions "asctime", "ctime", "gmtime", "localtime", "localeconv", "getenv", "setlocale" or "strerror" must not be used following a subsequent call to the same function

           Bug
        15. The "defined" preprocessor operator shall be used appropriately

           Bug
        16. The value of an object must not be read before it has been set

           Bug
        17. The built-in unary "-" operator should not be applied to an expression of unsigned type

           Bug
        18. The built-in relational operators ">", ">=", "<" and "<=" shall not be applied to objects of pointer type, except where they point to elements of the same array

           Bug
        19. Subtraction between pointers shall only be applied to pointers that address elements of the same array

           Bug
        20. Pointer arithmetic shall not form an invalid pointer

           Bug
        21. Operations on a memory location shall be sequenced appropriately

           Bug
        22. A function or object with external linkage should be "introduced" in a "header file"

           Code Smell
        23. The source code used to implement an "entity" shall appear only once

           Bug
        24. The "one-definition rule" shall not be violated

           Bug
        25. All "declarations" of a variable or function shall have the same type

           Bug
        26. A line whose first token is "#" shall be a valid preprocessing directive

           Bug
        27. An object or subobject must not be copied to an overlapping object

           Bug

        A line whose first token is "#" shall be a valid preprocessing directive

        intentionality - logical
        reliability
        Bug
        • unpredictable
        • 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 19.0.1 - A line whose first token is # shall be a valid preprocessing directive

        Category: Required

        Analysis: Decidable,Single Translation Unit

        Amplification

        This rule applies to all the lines within a translation unit, even if they are excluded by preprocessing.

        Note: white-space is permitted before and after the # token.

        Rationale

        A preprocessor directive may be used to conditionally exclude source code until a corresponding #else, #elif or #endif directive is encountered. A malformed or invalid preprocessing directive contained within the excluded source code may not be detected by the compiler, possibly leading to the exclusion of more code than was intended.

        Requiring all preprocessor directives to be syntactically valid, even when they occur within an excluded block of code, ensures that this cannot happen.

        Example

        In the following example all the code between the #ifndef and #endif directives may be excluded if AAA is defined. The developer intended that AAA be assigned to x, but the #else directive was entered incorrectly and not diagnosed by the compiler.

        #define AAA 2
        
        int32_t foo()
        {
          int32_t x = 0;
        
        #ifndef AAA
          x = 1;
        #else1        // Non-compliant
          x = AAA;
        #endif
        
          return x;
        }
        

        This rule does not apply to the following examples as the # is not a preprocessing token:

        // Not a preprocessing token within a comment \
        #not a token
        
        auto s = R"(
        #text)";      // Use in a raw string literal is not a preprocessing token
        

        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