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: 104 rules found
misra-c++2023
    Impact
      Clean code attribute
        1. A function call shall not violate the function's preconditions

           Bug
        2. Floating-point arithmetic should be used appropriately

           Bug
        3. The "goto" statement should not be used

           Code Smell
        4. An "integer-literal" of type "long long" shall not use a single "L" or "l" in any suffix

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

           Code Smell
        6. There shall be no occurrence of "undefined" or "critical unspecified behaviour"

           Bug
        7. User-defined identifiers shall have an appropriate form

           Code Smell
        8. "Global variables" shall not be used

           Code Smell
        9. The "volatile" qualifier shall be used appropriately

           Bug
        10. The built-in unary "+" operator should not be used

           Code Smell
        11. "Integral promotion" and the "usual arithmetic conversions" shall not change the signedness or the "type category" of an operand

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

           Bug
        13. The argument to a "mixed-use macro parameter" shall not be subject to further expansion

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

           Code Smell
        15. The library function "system" from "<cstdlib>" shall not be used

           Vulnerability
        16. 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
        17. Functions with "limited visibility" should be "used" at least once

           Code Smell
        18. Reads and writes on the same file stream shall be separated by a positioning operation

           Bug
        19. Line-splicing shall not be used in "//" comments

           Bug
        20. All variables should be initialized

           Code Smell
        21. Octal escape sequences, hexadecimal escape sequences and universal character names shall be terminated

           Code Smell
        22. Dynamic memory shall be managed automatically

           Code Smell
        23. Local variables shall not have static storage duration

           Code Smell
        24. The facilities provided by the standard "header file" "<csignal>" shall not be used

           Code Smell
        25. "Dynamic memory" should not be used

           Code Smell
        26. The macro "offsetof" shall not be used

           Code Smell
        27. 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
        28. The standard "header file" "<csetjmp>" shall not be used

           Code Smell
        29. The "#pragma" directive and the "_Pragma" operator should not be used

           Code Smell
        30. The "#" and "##" preprocessor operators should not be used

           Code Smell
        31. A macro parameter immediately following a "#" operator shall not be immediately followed by a "##" operator

           Code Smell
        32. The "#include" directive shall be followed by either a "<filename>" or ""filename"" sequence

           Bug
        33. The "'" or """ or "\" characters and the "/*" or "//" character sequences shall not occur in a "header file" name

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

           Code Smell
        35. 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
        36. The "defined" preprocessor operator shall be used appropriately

           Bug
        37. Program-terminating functions should not be used

           Code Smell
        38. A named bit-field with "signed integer type" shall not have a length of one bit

           Bug
        39. A bit-field shall have an appropriate type

           Code Smell
        40. Bit-fields should not be declared

           Code Smell
        41. Within an enumerator list, the value of an implicitly-specified "enumeration constant" shall be unique

           Code Smell
        42. The value of an object must not be read before it has been set

           Bug
        43. A conversion from function type to pointer-to-function type shall only occur in appropriate contexts

           Code Smell
        44. A function with non-"void" return type shall return a value on all paths

           Bug
        45. The parameters in all "declarations" or overrides of a function shall either be unnamed or have identical names

           Code Smell
        46. The features of "<cstdarg>" shall not be used

           Code Smell
        47. A "declaration" should not declare more than one variable or member variable

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

           Code Smell
        49. An assignment operator shall not assign the address of an object with automatic storage duration to an object with a greater lifetime

           Code Smell
        50. A function must not return a reference or a pointer to a local variable with automatic storage duration

           Bug
        51. The "asm" declaration shall not be used

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

           Code Smell
        53. The "goto" statement shall jump to a label declared later in the function body

           Code Smell
        54. A "goto" statement shall reference a label in a surrounding block

           Code Smell
        55. The structure of a "switch" statement shall be appropriate

           Code Smell
        56. All "if ... else if" constructs shall be terminated with an "else" statement

           Code Smell
        57. The body of an "iteration-statement" or a "selection-statement" shall be a "compound-statement"

           Code Smell
        58. The result of an assignment operator should not be "used"

           Code Smell
        59. An unsigned arithmetic operation with constant operands should not wrap

           Bug
        60. The comma operator should not be used

           Code Smell
        61. The right-hand operand of a logical "&&" or "||" operator should not contain "persistent side effects"

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

           Bug
        63. A cast should not convert a pointer type to an integral type

           Code Smell
        64. An object with integral, enumerated, or pointer to "void" type shall not be cast to a pointer type

           Code Smell
        65. Casts shall not be performed between a pointer to function and any other type

           Bug
        66. A cast shall not remove any "const" or "volatile" qualification from the type accessed via a pointer or by reference

           Code Smell
        67. The "declaration" of an object should contain no more than two levels of pointer indirection

           Code Smell
        68. 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
        69. Subtraction between pointers shall only be applied to pointers that address elements of the same array

           Bug
        70. Pointer arithmetic shall not form an invalid pointer

           Bug
        71. Parentheses should be used to make the meaning of an expression appropriately explicit

           Code Smell
        72. Operations on a memory location shall be sequenced appropriately

           Bug
        73. The names of the "standard signed integer types" and "standard unsigned integer types" should not be used

           Code Smell
        74. The same type aliases shall be used in all "declarations" of the same "entity"

           Code Smell
        75. A function or object with external linkage should be "introduced" in a "header file"

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

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

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

           Bug
        79. Block scope "declarations" shall not be "visually ambiguous"

           Code Smell
        80. A "header file" shall not contain definitions of functions or objects that are non-inline and have external linkage

           Code Smell
        81. A line whose first token is "#" shall be a valid preprocessing directive

           Bug
        82. All identifiers used in the controlling expression of "#if" or "#elif" preprocessing directives shall be defined prior to evaluation

           Bug
        83. Parentheses shall be used to ensure macro arguments are expanded appropriately

           Code Smell
        84. Tokens that look like a preprocessing directive shall not occur within a macro argument

           Bug
        85. Function-like macros shall not be defined

           Code Smell
        86. "#undef" should only be used for macros defined previously in the same file

           Code Smell
        87. "#include" directives should only be preceded by preprocessor directives or comments

           Code Smell
        88. String literals with different encoding prefixes shall not be concatenated

           Bug
        89. The lowercase form of "L" shall not be used as the first character in a literal suffix

           Code Smell
        90. Unsigned "integer literals" shall be appropriately suffixed

           Code Smell
        91. Octal constants shall not be used

           Code Smell
        92. Within character literals and non raw-string literals, "\" shall only be used to form a defined escape sequence or universal character name

           Bug
        93. A variable declared in an "inner scope" shall not hide a variable declared in an "outer scope"

           Code Smell
        94. Sections of code should not be "commented out"

           Code Smell
        95. The character sequence "/*" shall not be used within a C-style comment

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

           Code Smell
        97. An object or subobject must not be copied to an overlapping object

           Bug
        98. A named function parameter shall be "used" at least once

           Code Smell
        99. The value returned by a function shall be "used"

           Code Smell
        100. A value should not be "unnecessarily written" to a local object

           Code Smell
        101. Types with "limited visibility" should be "used" at least once

           Code Smell
        102. Variables with "limited visibility" should be "used" at least once

           Code Smell
        103. Controlling expressions should not be invariant

           Bug
        104. A function shall not contain "unreachable" statements

           Bug

        Variables with "limited visibility" should be "used" at least once

        intentionality - clear
        maintainability
        Code Smell
        • unused
        • misra-c++2023
        • misra-advisory

        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 0.2.1 - Variables with limited visibility should be used [1] at least once

        Category: Advisory

        Analysis: Decidable,Single Translation Unit

        Amplification

        A variable has limited visibility if it is not a function parameter, and it has internal linkage or no linkage.

        A variable is used [1] when:

        • It is part of an id-expression; or
        • The variable is of class type and has a user-provided constructor or a user-provided destructor.

        Rationale

        Variables that are declared and never used within a project do not contribute to program output; they constitute noise and may indicate that the wrong variable name has been used or that one or more statements are missing.

        Note: this rule allows the introduction of variables for the sole purpose of providing scoped resource allocation and release. For example:

        {
          std::lock_guard< std::mutex > lock { mutex };    // Compliant - has user-provided
                                                           //             constructor
          // ...
        } // User-provided destructor implicitly called here
        

        Exception

        This rule does not apply to:

        • Variables that have at least one declaration [2] with the [[maybe_unused]] attribute.
        • Constant variables at namespace scope that are declared within a header file [3].

        Example

        class C { };                  // No user-provided constructor or destructor
        
        namespace
        {
          C c;                        // Non-compliant - unused
        }
        
        void maybeUnused( int32_t a )
        {
          [[maybe_unused]]
            bool b = a > 0;           // Compliant (by exception #1 if NDEBUG is defined)
        
          assert( b );                // Does not use b if NDEBUG is defined
        
          usefn( a );
        }
        
        const int16_t x = 19;         // Compliant - x is read in initializedButNotUsed
        const int16_t y = 21;         // Non-compliant - would be compliant by exception #2
                                      //                 if declared in a header file
        
        void initializedButNotUsed()
        {
          int16_t local_1 = 42;       // Non-compliant - local_1 is never read
          int16_t local_2;            // Compliant
        
          local_2 = x;                // Use of local_2 for the purposes of this rule
        }
        
        void userProvidedCtor()
        {
          std::ifstream fs { "cfg.ini" };    // Compliant - user-provided constructor
        }
        

        Glossary

        [1] Use / used / using

        An object is used if:

        • It is the subject of a cast; or
        • It is explicitly initialized at declaration time; or
        • It is an operand in an expression; or
        • It is referenced.

        A function is used as defined in M23_331: MISRA C++ 2023 Rule 0.2.4.

        A type is used as defined in M23_005: MISRA C++ 2023 Rule 0.2.3.

        [2] Declaration

        A declaration introduces the name of an entity into a translation unit (see [basic.def]/1).

        An entity may be declared several times. The first declaration of an entity in a translation unit is called an introduction [4]. All subsequent declarations are called redeclarations [5].

        A definition [6] is a declaration, as described in [basic.def]/2.

        [3] Header file

        A header file is considered to be any file that is included during preprocessing (for example via the #include directive), regardless of its name or suffix.

        [4] Introduction

        See declaration [2].

        [5] Redeclaration

        See declaration [2].

        [6] Definition

        See declaration [2].

        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