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: 12 rules found
error-handling
    Impact
      Clean code attribute
        1. Move and swap operations should be "noexcept"

           Code Smell
        2. Exceptions should not be thrown in "noexcept" functions

           Code Smell
        3. Non-exception types should not be caught

           Code Smell
        4. Non-exception types should not be thrown

           Code Smell
        5. Destructors should be "noexcept"

           Bug
        6. General "catch" clauses should not be used

           Code Smell
        7. "catch" clauses should do more than rethrow

           Code Smell
        8. Exceptions should not be ignored

           Code Smell
        9. Exception specifications should not be used

           Code Smell
        10. Generic exceptions should not be caught

           Code Smell
        11. Try-catch blocks should not be nested

           Code Smell
        12. Generic exceptions should never be thrown

           Code Smell

        Non-exception types should not be caught

        consistency - conventional
        maintainability
        Code Smell
        • cppcoreguidelines
        • error-handling

        Why is this an issue?

        More Info

        Throwing as an exception an object that is not derived from std::exception is a bad practice. It is usually unreliable, meaningless, and a source of type clashes.

        For the same reason, catching a non-exception type is a sign that your application has a bad exception-handling design. You should use standard exception types or create your own exception types that inherit at some level from std::exception.

        Noncompliant code example

        try {
          /* code that can throw: 42 */
        } catch (int ex) { // Noncompliant
          if (ex == 42) {
            /*...*/
          }
        }
        

        Compliant solution

        try {
          /* code that can throw: std::domain_error("User ID not found.") */
        } catch (const std::domain_error& ex) {
          /*...*/
        }
        
          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