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: 22 rules found
unpredictable
    Impact
      Clean code attribute
        1. Globals should not depend on possibly not yet initialized variables

           Code Smell
        2. Coroutine should have co_return on each execution path or provide return_void

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

           Code Smell
        4. Arguments evaluation order should not be relied on

           Bug
        5. A single statement should not have more than one resource allocation

           Code Smell
        6. Functions that throw exceptions should not be used as hash functions

           Code Smell
        7. A call to "wait()" on a "std::condition_variable" should have a condition

           Bug
        8. Keywords shall not be used as macros identifiers

           Code Smell
        9. Incomplete types should not be deleted

           Code Smell
        10. Dereferenced null pointers should not be bound to references

           Code Smell
        11. Header guards should be followed by a matching "#define" macro

           Code Smell
        12. "memcmp" should only be called with pointers to trivially copyable types with no padding

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

           Bug
        14. Destructors should not be called explicitly

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

           Bug
        16. Reads and writes on the same file stream shall be separated by a positioning operation

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

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

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

           Bug
        20. Local variables shall not have static storage duration

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

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

           Bug

        Functions that throw exceptions should not be used as hash functions

        intentionality - logical
        maintainability
        Code Smell
        • cppcoreguidelines
        • unpredictable
        • since-c++11

        Why is this an issue?

        More Info

        You can provide your own hash function when using a standard library container based on a hash table (for instance, std::unordered_map). One of the requirements of the hash function is that it should not throw exceptions.

        If you don’t follow this requirement and your hash function throws, you may end up with corrupted data in your container.

        Since this function is not supposed to throw, you should also declare it noexcept.

        Noncompliant code example

        struct MyHash {
          size_t operator() (Customer c) const { // Noncompliant, copying may throw
            if (c.name().empty()) {
              throw std::runtime_error("You should know the customer name at this point"); // Noncompliant
            }
            return std::hash<std::string>()(c.name());
          }
        };
        std::unordered_set<Customer, MyHash> mySet;
        

        Compliant solution

        struct MyHash {
          size_t operator() (Customer const &c) const noexcept {
            return std::hash<std::string>()(c.name());
          }
        };
        std::unordered_set<Customer, MyHash> mySet;
        
          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.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use