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 798
  • Vulnerability14
  • Bug173
  • Security Hotspot19
  • Code Smell592

  • Quick Fix 99
Filtered: 79 rules found
suspicious
    Impact
      Clean code attribute
        1. "offsetof" macro should not be used

           Code Smell
        2. "errno" should not be used

           Code Smell
        3. Function names should be used either as a call with a parameter list or with the "&" operator

           Code Smell
        4. "enum" values should not be used as operands to built-in operators other than [ ], =, ==, !=, unary &, and the relational operators <, <=, >, >=

           Code Smell
        5. "bool" expressions should not be used as operands to built-in operators other than =, &&, ||, !, ==, !=, unary &, and the conditional operator

           Code Smell
        6. A cast shall not remove any const or volatile qualification from the type of a pointer or reference

           Code Smell
        7. Trigraphs should not be used

           Code Smell
        8. std::string_view::data() should not be passed to API expecting C-style strings

           Code Smell
        9. The condition of "assert" should not be trivially true

           Code Smell
        10. "std::format" numeric types should be 0-padded using the numerical padding and not the character padding

           Bug
        11. "std::format" should not have unused arguments

           Code Smell
        12. Type-constraints should not be used for forwarding reference parameters

           Bug
        13. Perfect forwarding constructors should be constrained

           Bug
        14. Requires-expression should not contain unevaluated concept checks or type predicates

           Bug
        15. Coroutine should have co_return on each execution path or provide return_void

           Bug
        16. Thread local variables should not be used in coroutines

           Code Smell
        17. The return value of "std::move" should be used in a function

           Code Smell
        18. "std::to_address" should be used to convert iterators to raw pointers

           Code Smell
        19. [[nodiscard]] should be used when the return value of a function should not be ignored

           Code Smell
        20. "dynamic_cast" should be used for downcasting

           Code Smell
        21. Pointers or references obtained from aliased smart pointers should not be used as function parameters

           Code Smell
        22. "#pragma pack" should be used correctly

           Bug
        23. Only valid arguments should be passed to UNIX/POSIX functions

           Code Smell
        24. Only valid arguments should be passed to stream functions

           Code Smell
        25. "Forwarding references" parameters should be used only to forward parameters

           Code Smell
        26. The order for arguments of the same type in a function call should be obvious

           Code Smell
        27. "std::move" and "std::forward" should not be confused

           Bug
        28. "std::move" should only be used where moving can happen

           Code Smell
        29. "^" should not be confused with exponentiation

           Code Smell
        30. An object with pointer type shall not be converted to an unrelated pointer type, either directly or indirectly

           Code Smell
        31. Size of variable length arrays should be greater than zero

           Code Smell
        32. "mktemp" family of functions templates should have at least six trailing "X"s

           Code Smell
        33. Unevaluated operands should not have side effects

           Code Smell
        34. Size argument of memory functions should be consistent

           Code Smell
        35. Return value of "nodiscard" functions should not be ignored

           Code Smell
        36. Implicit casts should not lower precision

           Code Smell
        37. "reinterpret_cast" should be used carefully

           Bug
        38. Appropriate size arguments should be passed to "strncat" and "strlcpy"

           Code Smell
        39. User-defined types should not be passed as variadic arguments

           Bug
        40. RAII objects should not be temporary

           Bug
        41. "std::auto_ptr" should not be used

           Bug
        42. Methods should not have identical implementations

           Code Smell
        43. Array values should not be replaced unconditionally

           Bug
        44. A conditionally executed single line should be denoted by indentation

           Code Smell
        45. Conditionals should start on new lines

           Code Smell
        46. "case" ranges should cover multiple values

           Code Smell
        47. Default capture should not be used

           Code Smell
        48. "switch" statements should cover all cases

           Code Smell
        49. Redundant pointer operator sequences should be removed

           Code Smell
        50. Members should be initialized in the order they are declared

           Code Smell
        51. Conditionally executed code should be reachable

           Bug
        52. Exceptions should not be ignored

           Code Smell
        53. Flexible array members should not be declared

           Code Smell
        54. Track parsing failures

           Code Smell
        55. Recursion should not be infinite

           Bug
        56. Two branches in a conditional structure should not have exactly the same implementation

           Code Smell
        57. Pre-defined macros should not be defined, redefined or undefined

           Code Smell
        58. Switch cases should end with an unconditional "break" statement

           Code Smell
        59. C-style memory allocation routines should not be used

           Code Smell
        60. "switch" statements should not contain non-case labels

           Code Smell
        61. Methods should not be empty

           Code Smell
        62. Assignments should not be made from within conditions

           Code Smell
        63. Variables should not be shadowed

           Code Smell
        64. Nested blocks of code should not be left empty

           Code Smell
        65. "using namespace" directives should not be used in header files

           Code Smell
        66. "Assignment" between numeric types shall be appropriate

           Code Smell
        67. There shall be no conversion from type "bool"

           Code Smell
        68. "Exception-unfriendly" functions shall be "noexcept"

           Code Smell
        69. The result of "std::remove", "std::remove_if", "std::unique" and "empty" shall be "used"

           Bug
        70. The argument to "std::move" shall be a non-const "lvalue"

           Code Smell
        71. A comparison of a "potentially virtual" pointer to member function shall only be with "nullptr"

           Bug
        72. Within an enumerator list, the value of an implicitly-specified "enumeration constant" shall be unique

           Code Smell
        73. A conversion from function type to pointer-to-function type shall only occur in appropriate contexts

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

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

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

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

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

           Code Smell
        79. All "declarations" of a variable or function shall have the same type

           Bug

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

        intentionality - complete
        reliability
        Code Smell
        • suspicious
        • 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 6.8.3 - An assignment operator shall not assign the address of an object with automatic storage duration to an object with a greater lifetime

        Category: Required

        Analysis: Decidable,Single Translation Unit

        Amplification

        This rule applies when the right-hand side of an assignment operator has the form &x, addressof( x ), or is the name of an object having array type.

        For the purposes of this rule, two objects with automatic storage duration that are declared in the same scope are considered to have the same lifetime.

        Rationale

        If the address of an automatic object is assigned to another automatic object of larger scope, or to an object with static storage duration, then the object containing the address may exist beyond the time when the original object ceases to exist (and its address becomes invalid).

        Note: this rule and M23_360: MISRA C++ 2023 Rule 6.8.1.

        Example

        void f1()
        {
          int8_t * p;
        
          {
            int8_t local;
            int8_t local_array[ 10 ];
        
            p = &local;                 // Non-compliant
            p = local_array;            // Non-compliant
          }
        }
        

        The following example is compliant with this rule, but violates M23_360: MISRA C++ 2023 Rule 6.8.1.

        void f2()
        {
          int8_t * p1;
        
          {
            int8_t * p2 = nullptr;
            int8_t local;
        
            p2 = &local;                // Compliant - objects have the same lifetime
            p1 = p2;                    // Rule does not apply
          }
        
          *p1 = 0;                      // Undefined behaviour
        }
        

        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