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: 58 rules found
misra-c++2023
    Impact
      Clean code attribute
        1. The character handling functions from "<cctype>" and "<cwctype>" shall not be used

           Code Smell
        2. The "goto" statement should not be used

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

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

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

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

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

           Bug
        8. "std::vector" should not be specialized with "bool"

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

           Code Smell
        10. The "setlocale" and "std::locale::global" functions shall not be called

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

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

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

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

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

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

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

           Bug
        18. All variables should be initialized

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

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

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

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

           Bug
        23. Variables should be captured explicitly in a non-"transient lambda"

           Code Smell
        24. Local variables shall not have static storage duration

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

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

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

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

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

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

           Bug
        31. 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
        32. An "empty throw" shall only occur within the "compound-statement" of a "catch handler"

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

           Bug
        34. Classes should not be inherited virtually

           Code Smell
        35. A named bit-field with "signed integer type" shall not have a length of one bit

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

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

           Bug
        38. A "declaration" should not declare more than one variable or member variable

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

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

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

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

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

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

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

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

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

           Bug
        48. The "declaration" of an object should contain no more than two levels of pointer indirection

           Code Smell
        49. "nullptr" shall be the only form of the "null-pointer-constant"

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

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

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

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

           Bug
        54. Function-like macros shall not be defined

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

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

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

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

           Code Smell

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

        intentionality - logical
        reliability
        Bug
        • symbolic-execution
        • unpredictable
        • misra-c++2023
        • misra-required

        Why is this an issue?

        More Info

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

        MISRA Rule 30.0.2

        Category: Required

        Analysis Type: Undecidable, System

        Amplification

        An explicit, interleaving stream positioning operation shall be used between input operations and output operations on a std::basic_filebuf.

        This rule applies to direct and indirect calls (e.g. from std::fstream) to std::basic_filebuf.

        Note: for the purposes of this rule, a call to fflush after an output operation is considered to be an explicit file positioning operation.

        Rationale

        The C FILE * abstraction, used as the underlying system file input/output for std::basic_filebuf, holds a single file position that is used when reading from or writing to the file. Using an input operation on a FILE * immediately after an output operation (or vice versa) results in undefined behaviour, unless an interleaving file positioning operation is used to update the file’s position.

        In addition, a streambuf object keeps separate buffer positions for reading and writing characters from its internal buffer. A basic_filebuf object is only guaranteed to synchronize the separate internal streambuf read and write positions that it maintains when a positioning operation is called when alternating between reading and writing (and vice versa). Failure to include such a positioning operation leads to undefined behaviour.

        The accessible positioning operations for streambuf are pubseekoff and pubseekpos, whilst for file streams they are tellg, seekg, tellp, and seekp. One of these functions shall be called when switching from output to input, or vice versa.

        Example

        void show_fstream_non_compliant()
        {
          std::fstream f { "hello.txt" };
        
          f << "Hello world!\n" << std::flush;   // flush is not a positioning operation
        
          std::string s {};
        
          std::getline( f, s );                  // Non-compliant - undefined behaviour
        }
        
        void show_fstream_compliant()
        {
          std::fstream f { "hello.txt" };
        
          f << "Hello world!\n";
        
          std::string s {};
        
          f.seekg( 0, std::ios_base::beg );
        
          std::getline(f, s);                    // Compliant - s holds "Hello world!"
        }
        

        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