Title: PVS-Studio_V  
Author: Will Snavely Mar 26, 2018
Last Changed by: Valery Oct 08, 2024
Tiny Link: (useful for email) https://wiki.sei.cmu.edu/confluence/x/nwF2Bg
Export As: Word · PDF  
Incoming Links
SEI CERT C Coding Standard (73)
    Page: DCL01-C. Do not reuse variable names in subscopes
    Page: ARR36-C. Do not subtract or compare two pointers that do not refer to the same array
    Page: ARR02-C. Explicitly specify array bounds, even if implicitly defined by an initializer
    Page: INT02-C. Understand integer conversion rules
    Page: MSC17-C. Finish every set of statements associated with a case label with a break statement
    Page: MEM03-C. Clear sensitive information stored in reusable resources
    Page: EXP42-C. Do not compare padding data
    Page: FLP06-C. Convert integers to floating point for floating-point operations
    Page: MSC12-C. Detect and remove code that has no effect or is never executed
    Page: MSC24-C. Do not use deprecated or obsolescent functions
    Page: API00-C. Functions should validate their parameters
    Page: ARR01-C. Do not apply the sizeof operator to a pointer when taking the size of an array
    Page: EXP19-C. Use braces for the body of an if, for, or while statement
    Page: FLP37-C. Do not use object representations to compare floating-point values
    Page: INT31-C. Ensure that integer conversions do not result in lost or misinterpreted data
    Page: MSC00-C. Compile cleanly at high warning levels
    Page: DCL37-C. Do not declare or define a reserved identifier
    Page: EXP45-C. Do not perform assignments in selection statements
    Page: DCL19-C. Minimize the scope of variables and functions
    Page: WIN30-C. Properly pair allocation and deallocation functions
    Page: ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
    Page: FIO30-C. Exclude user input from format strings
    Page: PRE01-C. Use parentheses within macros around parameter names
    Page: EXP16-C. Do not compare function pointers to constant values
    Page: FIO47-C. Use valid format strings
    Page: EXP36-C. Do not cast pointers into more strictly aligned pointer types
    Page: EXP39-C. Do not access a variable through a pointer of an incompatible type
    Page: EXP30-C. Do not depend on the order of evaluation for side effects
    Page: FIO40-C. Reset strings on fgets() or fgetws() failure
    Page: MEM30-C. Do not access freed memory
    Page: MSC21-C. Use robust loop termination conditions
    Page: INT32-C. Ensure that operations on signed integers do not result in overflow
    Page: DCL18-C. Do not begin integer constants with 0 when specifying a decimal value
    Page: EXP12-C. Do not ignore values returned by functions
    Page: STR30-C. Do not attempt to modify string literals
    Page: DCL30-C. Declare objects with appropriate storage durations
    Page: FLP34-C. Ensure that floating-point conversions are within range of the new type
    Page: EXP33-C. Do not read uninitialized memory
    Page: MEM34-C. Only free memory allocated dynamically
    Page: EXP08-C. Ensure pointer arithmetic is used correctly
    Page: FIO44-C. Only use values for fsetpos() that are returned from fgetpos()
    Page: ERR06-C. Understand the termination behavior of assert() and abort()
    Page: EXP44-C. Do not rely on side effects in operands to sizeof, _Alignof, or _Generic
    Page: EXP46-C. Do not use a bitwise operator with a Boolean-like operand
    Page: DCL11-C. Understand the type issues associated with variadic functions
    Page: MSC13-C. Detect and remove unused values
    Page: DCL41-C. Do not declare variables inside a switch statement before the first case label
    Page: EXP10-C. Do not depend on the order of evaluation of subexpressions or the order in which side effects take place
    Page: INT36-C. Converting a pointer to integer or integer to pointer
    Page: FLP02-C. Avoid using floating-point numbers when precise computation is needed
    Page: MSC15-C. Do not depend on undefined behavior
    Page: STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator
    Page: EXP13-C. Treat relational and equality operators as if they were nonassociative
    Page: INT34-C. Do not shift an expression by a negative number of bits or by greater than or equal to the number of bits that exist in the operand
    Page: INT33-C. Ensure that division and remainder operations do not result in divide-by-zero errors
    Page: DCL31-C. Declare identifiers before using them
    Page: EXP00-C. Use parentheses for precedence of operation
    Page: ENV30-C. Do not modify the object referenced by the return value of certain functions
    Page: STR32-C. Do not pass a non-null-terminated character sequence to a library function that expects a string
    Page: MEM31-C. Free dynamically allocated memory when no longer needed
    Page: INT30-C. Ensure that unsigned integer operations do not wrap
    Page: MEM35-C. Allocate sufficient memory for an object
    Page: MEM05-C. Avoid large stack allocations
    Page: EXP37-C. Call functions with the correct number and type of arguments
    Page: MSC06-C. Beware of compiler optimizations
    Page: PVS-Studio
    Page: FLP36-C. Preserve precision when converting integral values to floating-point type
    Page: INT00-C. Understand the data model used by your implementation(s)
    Page: CON43-C. Do not allow data races in multithreaded code
    Page: EXP34-C. Do not dereference null pointers
    Page: EXP15-C. Do not place a semicolon on the same line as an if, for, or while statement
    Page: FLP30-C. Do not use floating-point variables as loop counters
    Page: MSC01-C. Strive for logical completeness
Hierarchy
Parent Page
    Page: EE. Analyzers
Labels
There are no labels assigned to this page.