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
  • 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 315
  • Vulnerability13
  • Bug76
  • Security Hotspot19
  • Code Smell207

  • Quick Fix 19
 
Tags
    Impact
      Clean code attribute
        1. Pointer and reference parameters should be "const" if the corresponding object is not modified

           Code Smell
        2. Non-standard characters should not occur in header file names in "#include" directives

           Bug
        3. Functions should not be declared at block scope

           Code Smell
        4. Literal suffix "L" for long integers shall be upper case

           Code Smell
        5. Digraphs should not be used

           Code Smell
        6. The first element of an array should not be accessed implicitly

           Code Smell
        7. A single L in a literal suffix should only be used for long values

           Code Smell
        8. Loop variables should be declared in the minimal possible scope

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

           Code Smell
        10. "sizeof" should not be called on pointers

           Bug
        11. Control characters should not be used in literals

           Code Smell
        12. Parameters should be passed in the correct order

           Code Smell
        13. Redundant casts should not be used

           Code Smell
        14. Multiple variables should not be declared on the same line

           Code Smell
        15. Unused local variables should be removed

           Code Smell
        16. Octal values should not be used

           Code Smell
        17. A "while" loop should be used instead of a "for" loop

           Code Smell
        18. Sections of code should not be commented out

           Code Smell
        19. Redundant pairs of parentheses should be removed

           Code Smell

        "sizeof" should not be called on pointers

        intentionality - logical
        reliability
        Bug
        Quick FixIDE quick fixes available with SonarLint
        • cwe
        • cert

        Why is this an issue?

        More Info

        sizeof returns the size in bytes of a type. One common usage pattern, especially in C, is to use sizeof to determine the size of an array. However, arrays decay to pointers when passed as arguments to a function, and if sizeof is applied to such an argument, it will return the size of the pointer, not of the array. A similar issue happens when the array is used in an arithmetic operation.

        This rule raises issues when:

        • sizeof is used to compute the array size of a pointer passed as a function argument.
        • sizeof is called on the result of an arithmetic operation involving an array.

        Note: C++17 provides a std::size function that will correctly compute the number of elements of an array and fail to compile if provided with a pointer. It is simpler and safer to use this variant when available. C++20 also provides the functions std::ssize, std::ranges::size, and std::ranges::ssize with similar effects.

        Noncompliant code example

        void fun(int *data, int array[10]) {
          size_t const dataSize = sizeof data / sizeof(int); // Noncompliant, type of data is int *
          size_t const arraySize = sizeof array / sizeof(int); // Noncompliant, type of array is int * too
          int primes[] = { 1, 2, 3, 5, 7, 13, 17, 19};
          size_t const primesSize2 = sizeof(primes + 1) / sizeof(int); // Noncompliant, type of primes + 1 is int *
        }
        

        Compliant solution

        // Computing dataSize is now the responsibility of the caller
        void fun(int *data, int dataSize, int (&array)[10]) {
          size_t const arraySize = sizeof array / sizeof(int); // Compliant, no decay
          int primes[] = { 1, 2, 3, 5, 7, 13, 17, 19};
          size_t const primesSize = std::size(primes); // Better variant in C++17
          size_t const primesSize2 = sizeof primes / sizeof(int) + 1; // Compliant, type of primes is int[8]
        }
        
          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
          Developer Edition
          Available Since
          9.6

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use