Page Information

Title:	Polyspace Bug Finder
Author:	Will Snavely	Jan 05, 2017
Last Changed by:	David Svoboda	Oct 14, 2024
Tiny Link: (useful for email)	https://wiki.sei.cmu.edu/confluence/x/RdcxBQ
Export As:	Word · PDF

Incoming Links

SEI CERT C Coding Standard (110)
Page: FLP06-C. Convert integers to floating point for floating-point operations
Page: PRE11-C. Do not conclude macro definitions with a semicolon
Page: ARR32-C. Ensure size arguments for variable length arrays are in a valid range
Page: FLP30-C. Do not use floating-point variables as loop counters
Page: INT18-C. Evaluate integer expressions in a larger size before comparing or assigning to that size
Page: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction
Page: DCL01-C. Do not reuse variable names in subscopes
Page: ARR37-C. Do not add or subtract an integer to a pointer to a non-array object
Page: EXP45-C. Do not perform assignments in selection statements
Page: DCL37-C. Do not declare or define a reserved identifier
Page: MEM35-C. Allocate sufficient memory for an object
Page: CON43-C. Do not allow data races in multithreaded code
Page: EXP30-C. Do not depend on the order of evaluation for side effects
Page: MSC21-C. Use robust loop termination conditions
Page: ENV01-C. Do not make assumptions about the size of an environment variable
Page: CON35-C. Avoid deadlock by locking in a predefined order
Page: EXP15-C. Do not place a semicolon on the same line as an if, for, or while statement
Page: MEM03-C. Clear sensitive information stored in reusable resources
Page: FIO11-C. Take care when specifying the mode parameter of fopen()
Page: MSC13-C. Detect and remove unused values
Page: API04-C. Provide a consistent and usable error-checking mechanism
Page: PRE10-C. Wrap multistatement macros in a do-while loop
Page: MEM00-C. Allocate and free memory in the same module, at the same level of abstraction
Page: FIO02-C. Canonicalize path names originating from tainted sources
Page: FLP03-C. Detect and handle floating-point errors
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: DCL38-C. Use the correct syntax when declaring a flexible array member
Page: MSC24-C. Do not use deprecated or obsolescent functions
Page: EXP08-C. Ensure pointer arithmetic is used correctly
Page: ENV33-C. Do not call system()
Page: CON39-C. Do not join or detach a thread that was previously joined or detached
Page: EXP33-C. Do not read uninitialized memory
Page: MSC39-C. Do not call va_arg() on a va_list that has an indeterminate value
Page: DCL40-C. Do not create incompatible declarations of the same function or object
Page: MSC18-C. Be careful while handling sensitive data, such as passwords, in program code
Page: INT31-C. Ensure that integer conversions do not result in lost or misinterpreted data
Page: STR07-C. Use the bounds-checking interfaces for string manipulation
Page: MEM06-C. Ensure that sensitive data is not written out to disk
Page: FLP32-C. Prevent or detect domain and range errors in math functions
Page: EXP40-C. Do not modify constant objects
Page: MSC37-C. Ensure that control never reaches the end of a non-void function
Page: STR32-C. Do not pass a non-null-terminated character sequence to a library function that expects a string
Page: CON05-C. Do not perform operations that can block while holding a lock
Page: DCL11-C. Understand the type issues associated with variadic functions
Page: EXP05-C. Do not cast away a const qualification
Page: POS49-C. When data must be accessed by multiple threads, provide a mutex and guarantee no adjacent data is also accessed
Page: ARR01-C. Do not apply the sizeof operator to a pointer when taking the size of an array
Page: STR38-C. Do not confuse narrow and wide character strings and functions
Page: FIO46-C. Do not access a closed file
Page: INT02-C. Understand integer conversion rules
Page: ARR02-C. Explicitly specify array bounds, even if implicitly defined by an initializer
Page: FIO30-C. Exclude user input from format strings
Page: ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
Page: ARR39-C. Do not add or subtract a scaled integer to a pointer
Page: MEM30-C. Do not access freed memory
Page: PRE31-C. Avoid side effects in arguments to unsafe macros
Page: INT00-C. Understand the data model used by your implementation(s)
Page: POS51-C. Avoid deadlock with POSIX threads by locking in predefined order
Page: MSC30-C. Do not use the rand() function for generating pseudorandom numbers
Page: POS47-C. Do not use threads that can be canceled asynchronously
Page: MEM02-C. Immediately cast the result of a memory allocation function call into a pointer to the allocated type
Page: EXP39-C. Do not access a variable through a pointer of an incompatible type
Page: POS35-C. Avoid race conditions while checking for the existence of a symbolic link
Page: MSC32-C. Properly seed pseudorandom number generators
Page: EXP13-C. Treat relational and equality operators as if they were nonassociative
Page: EXP34-C. Do not dereference null pointers
Page: MEM04-C. Beware of zero-length allocations
Page: MSC33-C. Do not pass invalid data to the asctime() function
Page: WIN00-C. Be specific when dynamically loading libraries
Page: MSC07-C. Detect and remove dead code
Page: EXP32-C. Do not access a volatile object through a nonvolatile reference
Page: DCL36-C. Do not declare an identifier with conflicting linkage classifications
Page: DCL06-C. Use meaningful symbolic constants to represent literal values
Page: POS50-C. Declare objects shared between POSIX threads with appropriate storage durations
Page: CON32-C. Prevent data races when accessing bit-fields from multiple threads
Page: MEM31-C. Free dynamically allocated memory when no longer needed
Page: STR30-C. Do not attempt to modify string literals
Page: POS53-C. Do not use more than one mutex for concurrent waiting operations on a condition variable
Page: EXP43-C. Avoid undefined behavior when using restrict-qualified pointers
Page: STR02-C. Sanitize data passed to complex subsystems
Page: INT36-C. Converting a pointer to integer or integer to pointer
Page: MSC22-C. Use the setjmp(), longjmp() facility securely
Page: EXP37-C. Call functions with the correct number and type of arguments
Page: INT30-C. Ensure that unsigned integer operations do not wrap
Page: INT08-C. Verify that all integer values are in range
Page: FLP34-C. Ensure that floating-point conversions are within range of the new type
Page: DCL30-C. Declare objects with appropriate storage durations
Page: FIO21-C. Do not create temporary files in shared directories
Page: MEM05-C. Avoid large stack allocations
Page: MEM34-C. Only free memory allocated dynamically
Page: INT32-C. Ensure that operations on signed integers do not result in overflow
Page: INT10-C. Do not assume a positive remainder when using the % operator
Page: ENV30-C. Do not modify the object referenced by the return value of certain functions
Page: EXP36-C. Do not cast pointers into more strictly aligned pointer types
Page: MSC01-C. Strive for logical completeness
Page: DCL22-C. Use volatile for data that cannot be cached
Page: MEM11-C. Do not assume infinite heap space
Page: DCL31-C. Declare identifiers before using them
Page: INT04-C. Enforce limits on integer values originating from tainted sources
Page: POS52-C. Do not perform operations that can block while holding a POSIX lock
Page: MSC12-C. Detect and remove code that has no effect or is never executed
Page: FIO45-C. Avoid TOCTOU race conditions while accessing files
Page: POS05-C. Limit access to files by creating a jail
Page: STR11-C. Do not specify the bound of a character array initialized with a string literal
Page: EXP00-C. Use parentheses for precedence of operation
Page: STR03-C. Do not inadvertently truncate a string
Page: MEM12-C. Consider using a goto chain when leaving a function on error when using and releasing resources
Page: MSC41-C. Never hard code sensitive information
Page: INT33-C. Ensure that division and remainder operations do not result in divide-by-zero errors
Page: INT35-C. Use correct integer precisions

SEI CERT C++ Coding Standard (13)
Page: DCL55-CPP. Avoid information leakage when passing a class object across a trust boundary
Page: MEM53-CPP. Explicitly construct and destruct objects when manually managing object lifetime
Page: STR52-CPP. Use valid references, pointers, and iterators to reference elements of a basic_string
Page: CTR53-CPP. Use valid iterator ranges
Page: CTR54-CPP. Do not subtract iterators that do not refer to the same container
Page: CTR55-CPP. Do not use an additive operator on an iterator if the result would overflow
Page: ERR59-CPP. Do not throw an exception across execution boundaries
Page: EXP51-CPP. Do not delete an array through a pointer of the incorrect type
Page: CTR52-CPP. Guarantee that library functions do not overflow
Page: EXP62-CPP. Do not access the bits of an object representation that are not part of the object's value representation
Page: CTR51-CPP. Use valid references, pointers, and iterators to reference elements of a container
Page: STR51-CPP. Do not attempt to create a std::string from a null pointer
Page: DCL56-CPP. Avoid cycles during initialization of static objects

Hierarchy

Parent Page
Page: EE. Analyzers

Labels

Global Labels (1)

analyzer

Recent Changes

Time	Editor
Oct 14, 2024 07:27	David Svoboda	View Changes
Feb 08, 2024 09:06	David Svoboda	View Changes
Sep 27, 2023 08:25	David Svoboda	View Changes
Jul 13, 2023 13:28	David Svoboda	View Changes
Jun 06, 2023 12:24	David Svoboda