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: 17 rules found
misra-advisory
    Impact
      Clean code attribute
        1. The "goto" statement should not be used

           Code Smell
        2. "std::vector" should not be specialized with "bool"

           Code Smell
        3. Variables of array type should not be declared

           Code Smell
        4. "Unscoped enumerations" should not be declared

           Code Smell
        5. Functions with "limited visibility" should be "used" at least once

           Code Smell
        6. All variables should be initialized

           Code Smell
        7. Variables should be captured explicitly in a non-"transient lambda"

           Code Smell
        8. The "#" and "##" preprocessor operators should not be used

           Code Smell
        9. A "noexcept" function should not attempt to propagate an exception to the calling function

           Bug
        10. Classes should not be inherited virtually

           Code Smell
        11. A "declaration" should not declare more than one variable or member variable

           Code Smell
        12. There should be no unnamed namespaces in "header files"

           Code Smell
        13. A cast should not convert a pointer type to an integral type

           Code Smell
        14. The "declaration" of an object should contain no more than two levels of pointer indirection

           Code Smell
        15. The names of the "standard signed integer types" and "standard unsigned integer types" should not be used

           Code Smell
        16. "#include" directives should only be preceded by preprocessor directives or comments

           Code Smell
        17. Variables with "limited visibility" should be "used" at least once

           Code Smell

        A "noexcept" function should not attempt to propagate an exception to the calling function

        intentionality - logical
        reliability
        Bug
        • misra-c++2023
        • misra-advisory

        Why is this an issue?

        More Info

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

        MISRA Rule 18.5.1

        Category: Advisory

        Analysis Type: Undecidable,System

        Amplification

        A noexcept function attempts to propagate an exception when it directly or indirectly throws an exception that is not caught within the function. Any exception that would escape the function causes the program to terminate.

        This rule also applies to all functions that are implicitly noexcept.

        If a function’s exception-specifier is of the form noexcept( condition ), then the function is only permitted to throw an exception when the condition is false.

        A function’s compliance with this rule is independent of the context in which it is called.

        Rationale

        Marking a function noexcept or noexcept( true ) does not prevent an exception from being raised in the body of the function. However, if the function attempts to propagate an exception to a calling function, the program will be terminated through a call to std::terminate. This results in implementation-defined behaviour, including whether or not the stack is unwound before the program terminates (which may result in dangling resources).

        Example

        void mayThrow( int32_t x )
        {
          if ( x < 0 )
          {
            throw std::exception {};
          }
        }
        
        void notThrowing()
        {
        }
        
        void f1( int32_t x ) noexcept    // Compliant
        {
          notThrowing();
        }
        
        void f2( int32_t x ) noexcept    // Compliant
        {
          if ( x > 0 )                   // This guard ...
          {
            mayThrow( x );               // ... ensures the call to mayThrow cannot throw
          }
        }
        
        void f3( int32_t x ) noexcept    // Non-compliant - even if f3 is only called in
        {                                // contexts where x > 0
          mayThrow( x );
        }
        
        void f4( int32_t x ) noexcept    // Compliant - any exception will not propagate
        {
          try
          {
            mayThrow( x );
          }
          catch( ... )
          {
          }
        }
        
        void f5( int32_t x ) noexcept    // Non-compliant - exception is rethrown
        {
          try
          {
            mayThrow( x );
          }
          catch ( ... )
          {
            throw;
          }
        }
        

        Instantiations of the following template are compliant as they will only be noexcept( true ) when the addition is non-throwing:

        template< class T >                                 // Compliant
        T plus( T a, T b ) noexcept( noexcept( a + b ) )
        {
          return a + b;
        }
        
        class A
        {
          ~A()
          {
            throw std::exception {};   // Non-compliant - destructor is implicitly noexcept
          }
        };
        
        void f6( int32_t x ) throw()   // throw() makes function noexcept
        {
          throw std::exception {};     // Non-compliant
        }
        

        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