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
 
Tags
    Impact
      Clean code attribute
        1. "abort", "exit", "getenv" and "system" from <stdlib.h> should not be used

           Bug
        2. "atof", "atoi" and "atol" from <stdlib.h> should not be used

           Bug
        3. "<signal.h>" should not be used

           Bug
        4. Dynamic heap memory allocation should not be used

           Bug
        5. Lines starting with "#" should contain valid preprocessing directives

           Bug
        6. Macros used in preprocessor directives should be defined before use

           Bug
        7. Function-like macros should not be invoked without all of their arguments

           Bug
        8. "#include" directives should be followed by either <filename> or "filename" sequences

           Bug
        9. Non-standard characters should not occur in header file names in "#include" directives

           Bug
        10. The address of an automatic object should not be assigned to another object that may persist after the first object has ceased to exist

           Bug
        11. Function exit paths should have appropriate return values

           Bug
        12. The number of arguments passed to a function should match the number of parameters

           Bug
        13. Evaluation of the operand to the sizeof operator shall not contain side effects

           Bug
        14. Non-empty statements should change control flow or have at least one side-effect

           Bug
        15. Unary minus should not be applied to an unsigned expression

           Bug
        16. Bitwise operators should not be applied to signed operands

           Bug
        17. Boolean operations should not have numeric operands, and vice versa

           Bug
        18. Objects with integer type should not be converted to objects with pointer type

           Bug
        19. Pointer conversions should be restricted to a safe subset

           Bug
        20. Function pointers should not be converted to any other type

           Bug
        21. Results of ~ and << operations on operands of underlying types unsigned char and unsigned short should immediately be cast to the operand's underlying type

           Bug
        22. Variables should be initialized before use

           Bug
        23. String literals with different prefixes should not be concatenated

           Bug
        24. Only escape sequences defined in the ISO C standard should be used

           Bug
        25. Macro arguments should not contain preprocessing directives

           Bug
        26. Variables should not be accessed outside of their scope

           Bug
        27. "volatile" should not be used to qualify objects for which the meaning is not defined

           Bug
        28. Relational and subtraction operators should not be used with pointers to different arrays

           Bug
        29. Arguments evaluation order should not be relied on

           Bug
        30. "#pragma pack" should be used correctly

           Bug
        31. Enums should be consistent with the bit fields they initialize

           Bug
        32. "pthread_mutex_t" should be unlocked in the reverse order they were locked

           Bug
        33. "pthread_mutex_t" should be properly initialized and destroyed

           Bug
        34. "pthread_mutex_t" should not be locked when already locked, or unlocked when already unlocked

           Bug
        35. User-defined types should not be passed as variadic arguments

           Bug
        36. Functions with "noreturn" attribute should not return

           Bug
        37. "memcmp" should only be called with pointers to trivially copyable types with no padding

           Bug
        38. Array values should not be replaced unconditionally

           Bug
        39. Integral operations should not overflow

           Bug
        40. "case" ranges should not be empty

           Bug
        41. All branches in a conditional structure should not have exactly the same implementation

           Bug
        42. Parameter values should be appropriate

           Bug
        43. Declaration specifiers should not be redundant

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

           Bug
        45. Closed resources should not be accessed

           Bug
        46. Dynamically allocated memory should be released

           Bug
        47. Freed memory should not be used

           Bug
        48. Memory locations should not be released more than once

           Bug
        49. Memory access should be explicitly bounded to prevent buffer overflows

           Bug
        50. Zero should not be a possible denominator

           Bug
        51. "sizeof" should not be called on pointers

           Bug
        52. Unary prefix operators should not be repeated

           Bug
        53. Non-existent operators like "=+" should not be used

           Bug
        54. Values of different "enum" types should not be compared

           Bug
        55. The "sizeof" and "alignof" operator should not be used with operands of a "void" type

           Bug
        56. "nonnull" parameters and return values of "returns_nonnull" functions should not be null

           Bug
        57. Conditionally executed code should be reachable

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

           Bug
        59. Line-splicing should not be used in "//" comments

           Bug
        60. Printf-style format strings should not lead to unexpected behavior at runtime

           Bug
        61. Null pointers should not be dereferenced

           Bug
        62. Single-bit named bit fields should not be of a signed type

           Bug
        63. "for" loop counters should not have essentially floating type

           Bug
        64. Recursion should not be infinite

           Bug
        65. Values should not be uselessly incremented

           Bug
        66. Resources should be closed

           Bug
        67. Line continuation characters '\' should not be followed by trailing whitespace

           Bug
        68. "sizeof(sizeof(...))" should not be used

           Bug
        69. Related "if/else if" statements should not have the same condition

           Bug
        70. Pointers should not be cast to integral types

           Bug
        71. Identical expressions should not be used on both sides of a binary operator

           Bug
        72. All code should be reachable

           Bug
        73. Loops with at most one iteration should be refactored

           Bug
        74. Variables should not be self-assigned

           Bug
        75. Floating point numbers should not be tested for equality

           Bug
        76. Function parameters' initial values should not be ignored

           Bug
        77. A function call shall not violate the function's preconditions

           Bug
        78. Floating-point arithmetic should be used appropriately

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

           Bug
        80. The "volatile" qualifier shall be used appropriately

           Bug
        81. The operands of "bitwise operators" and "shift operators" shall be appropriate

           Bug
        82. 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
        83. Reads and writes on the same file stream shall be separated by a positioning operation

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

           Bug
        85. 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
        86. The "#include" directive shall be followed by either a "<filename>" or ""filename"" sequence

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

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

           Bug
        89. A named bit-field with "signed integer type" shall not have a length of one bit

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

           Bug
        91. A function with non-"void" return type shall return a value on all paths

           Bug
        92. A function must not return a reference or a pointer to a local variable with automatic storage duration

           Bug
        93. An unsigned arithmetic operation with constant operands should not wrap

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

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

           Bug
        96. Casts shall not be performed between a pointer to function and any other type

           Bug
        97. 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
        98. Subtraction between pointers shall only be applied to pointers that address elements of the same array

           Bug
        99. Pointer arithmetic shall not form an invalid pointer

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

           Bug
        101. The source code used to implement an "entity" shall appear only once

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

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

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

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

           Bug
        106. Tokens that look like a preprocessing directive shall not occur within a macro argument

           Bug
        107. String literals with different encoding prefixes shall not be concatenated

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

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

           Bug
        110. Controlling expressions should not be invariant

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

           Bug

        A function call shall not violate the function's preconditions

        intentionality - logical
        reliability
        Bug
        • misra-c++2023
        • misra-required
        • misra-directive

        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.

        Dir 0.3.2 - A function call shall not violate the function’s preconditions

        Category: Required

        Rationale

        Violating a function’s implicit or explicit preconditions may lead to it exhibiting unexpected results or having undefined behaviour.

        Example

        float f( float a )
        {
          return fmodf( a, 0.0f );      // 'fmodf' requires a non zero value
        }
        
        // Precondition for 'b1' is that 'v' is not empty
        int32_t b1( std::vector< int32_t > const & v )
        {
          return v.front ();
        }
        
        int32_t b2()
        {
          std::vector< int32_t > v;
        
          return b1( v );            // Violates the precondition of b1
        }
        

        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