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 674
  • Vulnerability13
  • Bug139
  • Security Hotspot19
  • Code Smell503

  • Quick Fix 91
Filtered: 40 rules found
misra-required
    Impact
      Clean code attribute
        1. The character handling functions from "<cctype>" and "<cwctype>" shall not be used

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

           Code Smell
        3. A non-"transient lambda" shall not implicitly capture "this"

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

           Code Smell
        5. An object shall not be accessed outside of its lifetime

           Bug
        6. A function declared with the "[[noreturn]]" attribute shall not return

           Bug
        7. The "setlocale" and "std::locale::global" functions shall not be called

           Code Smell
        8. An "explicit type conversion" shall not be an "expression statement"

           Bug
        9. "Advanced memory management" shall not be used

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

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

           Bug
        12. A pointer to an incomplete "class" type shall not be deleted

           Bug
        13. The result of "std::remove", "std::remove_if", "std::unique" and "empty" shall be "used"

           Bug
        14. An object shall not be used while in a "potentially moved-from state"

           Code Smell
        15. "Forwarding references" and "std::forward" shall be used together

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

           Bug
        17. Local variables shall not have static storage duration

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

           Code Smell
        19. The standard "header file" "<csetjmp>" shall not be used

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

           Bug
        21. An exception of "class" type shall be caught by "const" reference or reference

           Bug
        22. Handlers for a "function-try-block" of a constructor or destructor shall not refer to non-static members from their class or its bases

           Bug
        23. An "empty throw" shall only occur within the "compound-statement" of a "catch handler"

           Code Smell
        24. An exception object shall not have pointer type

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

           Bug
        26. The "union" keyword shall not be used

           Code Smell
        27. The identifier "main" shall not be used for a function other than the global function "main"

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

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

           Code Smell
        30. The "address-of" operator shall not be overloaded

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

           Code Smell
        32. C-style casts and "functional notation" casts shall not be used

           Code Smell
        33. A virtual base class shall only be cast to a derived class by means of "dynamic_cast"

           Bug
        34. "nullptr" shall be the only form of the "null-pointer-constant"

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

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

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

           Bug
        38. Function-like macros shall not be defined

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

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

           Code Smell

        An exception object shall not have pointer type

        intentionality - clear
        reliability
        Bug
        • pitfall
        • misra-c++2023
        • misra-required

        Why is this an issue?

        More Info

        This rule is part of MISRA C++:2023.

        MISRA Rule 18.1.1

        Category: Required

        Analysis Type: Decidable,Single Translation Unit

        Rationale

        If an exception object of pointer type is thrown and that pointer refers to a dynamically created object, then it may be unclear which function is responsible for destroying it, and when. This ambiguity does not exist if the object is thrown by value.

        Example

        class A
        {
          // Implementation
        };
        
        void fn( int16_t i )
        {
          static A   a1;
                 A * a2 = new A;
        
          if ( i > 10 )
          {
            throw &a1;              // Non-compliant - pointer type thrown
          }
        
          else
          {
            throw a2;               // Non-compliant - pointer type thrown
          }
        }
        

        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

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use