Page Information

Title:	Polyspace Bug Finder_V
Author:	Will Snavely	Jan 05, 2017
Last Changed by:	Anirban Gangopadhyay	May 03, 2024
Tiny Link: (useful for email)	https://wiki.sei.cmu.edu/confluence/x/Q9cxBQ
Export As:	Word · PDF

Incoming Links

SEI CERT C Coding Standard (205)
Page: FIO32-C. Do not perform operations on devices that are only appropriate for files
Page: POS47-C. Do not use threads that can be canceled asynchronously
Page: EXP35-C. Do not modify objects with temporary lifetime
Page: PRE31-C. Avoid side effects in arguments to unsafe macros
Page: POS39-C. Use the correct byte ordering when transferring data between systems
Page: STR34-C. Cast characters to unsigned char before converting to larger integer sizes
Page: FIO30-C. Exclude user input from format strings
Page: POS37-C. Ensure that privilege relinquishment is successful
Page: POS05-C. Limit access to files by creating a jail
Page: FIO24-C. Do not open a file that is already open
Page: PRE01-C. Use parentheses within macros around parameter names
Page: CON32-C. Prevent data races when accessing bit-fields from multiple threads
Page: DCL19-C. Minimize the scope of variables and functions
Page: WIN30-C. Properly pair allocation and deallocation functions
Page: PRE07-C. Avoid using repeated question marks
Page: POS35-C. Avoid race conditions while checking for the existence of a symbolic link
Page: MSC33-C. Do not pass invalid data to the asctime() function
Page: INT14-C. Avoid performing bitwise and arithmetic operations on the same data
Page: FLP00-C. Understand the limitations of floating-point numbers
Page: FIO47-C. Use valid format strings
Page: INT12-C. Do not make assumptions about the type of a plain int bit-field when used in an expression
Page: CON37-C. Do not call signal() in a multithreaded program
Page: DCL15-C. Declare file-scope objects or functions that do not need external linkage as static
Page: ERR00-C. Adopt and implement a consistent and comprehensive error-handling policy
Page: MEM30-C. Do not access freed memory
Page: FIO41-C. Do not call getc(), putc(), getwc(), or putwc() with a stream argument that has side effects
Page: MEM12-C. Consider using a goto chain when leaving a function on error when using and releasing resources
Page: DCL30-C. Declare objects with appropriate storage durations
Page: EXP46-C. Do not use a bitwise operator with a Boolean-like operand
Page: ARR02-C. Explicitly specify array bounds, even if implicitly defined by an initializer
Page: Polyspace Bug Finder
Page: FIO44-C. Only use values for fsetpos() that are returned from fgetpos()
Page: INT35-C. Use correct integer precisions
Page: STR32-C. Do not pass a non-null-terminated character sequence to a library function that expects a string
Page: EXP00-C. Use parentheses for precedence of operation
Page: POS38-C. Beware of race conditions when using fork and file descriptors
Page: DCL00-C. Const-qualify immutable objects
Page: ERR32-C. Do not rely on indeterminate values of errno
Page: POS36-C. Observe correct revocation order while relinquishing privileges
Page: MSC22-C. Use the setjmp(), longjmp() facility securely
Page: CON38-C. Preserve thread safety and liveness when using condition variables
Page: DCL31-C. Declare identifiers before using them
Page: FIO34-C. Distinguish between characters read from a file and EOF or WEOF
Page: DCL10-C. Maintain the contract between the writer and caller of variadic functions
Page: MEM05-C. Avoid large stack allocations
Page: FLP32-C. Prevent or detect domain and range errors in math functions
Page: PRE00-C. Prefer inline or static functions to function-like macros
Page: EXP37-C. Call functions with the correct number and type of arguments
Page: MSC39-C. Do not call va_arg() on a va_list that has an indeterminate value
Page: EXP12-C. Do not ignore values returned by functions
Page: INT00-C. Understand the data model used by your implementation(s)
Page: EXP30-C. Do not depend on the order of evaluation for side effects
Page: FIO02-C. Canonicalize path names originating from tainted sources
Page: POS53-C. Do not use more than one mutex for concurrent waiting operations on a condition variable
Page: MSC24-C. Do not use deprecated or obsolescent functions
Page: FIO11-C. Take care when specifying the mode parameter of fopen()
Page: FLP34-C. Ensure that floating-point conversions are within range of the new type
Page: CON31-C. Do not destroy a mutex while it is locked
Page: DCL36-C. Do not declare an identifier with conflicting linkage classifications
Page: MSC40-C. Do not violate constraints
Page: DCL38-C. Use the correct syntax when declaring a flexible array member
Page: POS30-C. Use the readlink() function properly
Page: INT18-C. Evaluate integer expressions in a larger size before comparing or assigning to that size
Page: ENV34-C. Do not store pointers returned by certain functions
Page: FLP03-C. Detect and handle floating-point errors
Page: FIO38-C. Do not copy a FILE object
Page: FIO37-C. Do not assume that fgets() or fgetws() returns a nonempty string when successful
Page: SIG34-C. Do not call signal() from within interruptible signal handlers
Page: ENV32-C. All exit handlers must return normally
Page: MSC20-C. Do not use a switch statement to transfer control into a complex block
Page: MSC37-C. Ensure that control never reaches the end of a non-void function
Page: PRE09-C. Do not replace secure functions with deprecated or obsolescent functions
Page: DCL39-C. Avoid information leakage when passing a structure across a trust boundary
Page: ARR36-C. Do not subtract or compare two pointers that do not refer to the same array
Page: ERR33-C. Detect and handle standard library errors
Page: INT07-C. Use only explicitly signed or unsigned char type for numeric values
Page: PRE30-C. Do not create a universal character name through concatenation
Page: MEM01-C. Store a new value in pointers immediately after free()
Page: CON34-C. Declare objects shared between threads with appropriate storage durations
Page: FLP37-C. Do not use object representations to compare floating-point values
Page: STR11-C. Do not specify the bound of a character array initialized with a string literal
Page: EXP47-C. Do not call va_arg with an argument of the incorrect type
Page: FLP02-C. Avoid using floating-point numbers when precise computation is needed
Page: EXP44-C. Do not rely on side effects in operands to sizeof, _Alignof, or _Generic
Page: POS50-C. Declare objects shared between POSIX threads with appropriate storage durations
Page: DCL13-C. Declare function parameters that are pointers to values not changed by the function as const
Page: DCL02-C. Use visually distinct identifiers
Page: PRE10-C. Wrap multistatement macros in a do-while loop
Page: ENV31-C. Do not rely on an environment pointer following an operation that may invalidate it
Page: DCL40-C. Do not create incompatible declarations of the same function or object
Page: MEM02-C. Immediately cast the result of a memory allocation function call into a pointer to the allocated type
Page: EXP32-C. Do not access a volatile object through a nonvolatile reference
Page: EXP36-C. Do not cast pointers into more strictly aligned pointer types
Page: FIO42-C. Close files when they are no longer needed
Page: DCL01-C. Do not reuse variable names in subscopes
Page: SIG31-C. Do not access shared objects in signal handlers
Page: STR30-C. Do not attempt to modify string literals
Page: EXP13-C. Treat relational and equality operators as if they were nonassociative
Page: MSC32-C. Properly seed pseudorandom number generators
Page: INT36-C. Converting a pointer to integer or integer to pointer
Page: INT08-C. Verify that all integer values are in range
Page: DCL18-C. Do not begin integer constants with 0 when specifying a decimal value
Page: FLP06-C. Convert integers to floating point for floating-point operations
Page: DCL23-C. Guarantee that mutually visible identifiers are unique
Page: ARR39-C. Do not add or subtract a scaled integer to a pointer
Page: CON40-C. Do not refer to an atomic variable twice in an expression
Page: POS54-C. Detect and handle POSIX library errors
Page: MEM33-C. Allocate and copy structures containing a flexible array member dynamically
Page: EXP05-C. Do not cast away a const qualification
Page: WIN00-C. Be specific when dynamically loading libraries
Page: ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
Page: EXP34-C. Do not dereference null pointers
Page: STR38-C. Do not confuse narrow and wide character strings and functions
Page: FIO46-C. Do not access a closed file
Page: ERR30-C. Take care when reading errno
Page: EXP33-C. Do not read uninitialized memory
Page: DCL16-C. Use "L," not "l," to indicate a long value
Page: MSC17-C. Finish every set of statements associated with a case label with a break statement
Page: INT02-C. Understand integer conversion rules
Page: INT10-C. Do not assume a positive remainder when using the % operator
Page: MSC41-C. Never hard code sensitive information
Page: CON05-C. Do not perform operations that can block while holding a lock
Page: EXP10-C. Do not depend on the order of evaluation of subexpressions or the order in which side effects take place
Page: EXP19-C. Use braces for the body of an if, for, or while statement
Page: POS49-C. When data must be accessed by multiple threads, provide a mutex and guarantee no adjacent data is also accessed
Page: MEM06-C. Ensure that sensitive data is not written out to disk
Page: MSC12-C. Detect and remove code that has no effect or is never executed
Page: MEM31-C. Free dynamically allocated memory when no longer needed
Page: MSC38-C. Do not treat a predefined identifier as an object if it might only be implemented as a macro
Page: FIO45-C. Avoid TOCTOU race conditions while accessing files
Page: DCL11-C. Understand the type issues associated with variadic functions
Page: DCL06-C. Use meaningful symbolic constants to represent literal values
Page: ENV33-C. Do not call system()
Page: EXP08-C. Ensure pointer arithmetic is used correctly
Page: INT30-C. Ensure that unsigned integer operations do not wrap
Page: STR37-C. Arguments to character-handling functions must be representable as an unsigned char
Page: EXP09-C. Use sizeof to determine the size of a type or variable
Page: INT31-C. Ensure that integer conversions do not result in lost or misinterpreted data
Page: ERR34-C. Detect errors when converting a string to a number
Page: MEM36-C. Do not modify the alignment of objects by calling realloc()
Page: SIG30-C. Call only asynchronous-safe functions within signal handlers
Page: ENV30-C. Do not modify the object referenced by the return value of certain functions
Page: MSC01-C. Strive for logical completeness
Page: POS34-C. Do not call putenv() with a pointer to an automatic variable as the argument
Page: MEM34-C. Only free memory allocated dynamically
Page: MSC30-C. Do not use the rand() function for generating pseudorandom numbers
Page: POS51-C. Avoid deadlock with POSIX threads by locking in predefined order
Page: MSC15-C. Do not depend on undefined behavior
Page: MSC13-C. Detect and remove unused values
Page: MEM03-C. Clear sensitive information stored in reusable resources
Page: CON33-C. Avoid race conditions when using library functions
Page: POS48-C. Do not unlock or destroy another POSIX thread's mutex
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: ENV01-C. Do not make assumptions about the size of an environment variable
Page: CON41-C. Wrap functions that can fail spuriously in a loop
Page: STR02-C. Sanitize data passed to complex subsystems
Page: CON43-C. Do not allow data races in multithreaded code
Page: INT09-C. Ensure enumeration constants map to unique values
Page: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction
Page: FIO39-C. Do not alternately input and output from a stream without an intervening flush or positioning call
Page: API04-C. Provide a consistent and usable error-checking mechanism
Page: ARR32-C. Ensure size arguments for variable length arrays are in a valid range
Page: POS44-C. Do not use signals to terminate threads
Page: EXP42-C. Do not compare padding data
Page: PRE11-C. Do not conclude macro definitions with a semicolon
Page: STR07-C. Use the bounds-checking interfaces for string manipulation
Page: EXP45-C. Do not perform assignments in selection statements
Page: CON36-C. Wrap functions that can spuriously wake up in a loop
Page: DCL37-C. Do not declare or define a reserved identifier
Page: MSC21-C. Use robust loop termination conditions
Page: FLP30-C. Do not use floating-point variables as loop counters
Page: ARR37-C. Do not add or subtract an integer to a pointer to a non-array object
Page: INT33-C. Ensure that division and remainder operations do not result in divide-by-zero errors
Page: MSC04-C. Use comments consistently and in a readable fashion
Page: DCL22-C. Use volatile for data that cannot be cached
Page: DCL12-C. Implement abstract data types using opaque types
Page: CON30-C. Clean up thread-specific storage
Page: ARR38-C. Guarantee that library functions do not form invalid pointers
Page: POS52-C. Do not perform operations that can block while holding a POSIX lock
Page: PRE06-C. Enclose header files in an include guard
Page: CON39-C. Do not join or detach a thread that was previously joined or detached
Page: INT04-C. Enforce limits on integer values originating from tainted sources
Page: ARR01-C. Do not apply the sizeof operator to a pointer when taking the size of an array
Page: STR03-C. Do not inadvertently truncate a string
Page: INT32-C. Ensure that operations on signed integers do not result in overflow
Page: DCL41-C. Do not declare variables inside a switch statement before the first case label
Page: FLP36-C. Preserve precision when converting integral values to floating-point type
Page: STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator
Page: EXP40-C. Do not modify constant objects
Page: FIO21-C. Do not create temporary files in shared directories
Page: MEM11-C. Do not assume infinite heap space
Page: CON35-C. Avoid deadlock by locking in a predefined order
Page: FIO40-C. Reset strings on fgets() or fgetws() failure
Page: MEM35-C. Allocate sufficient memory for an object
Page: EXP15-C. Do not place a semicolon on the same line as an if, for, or while statement
Page: EXP39-C. Do not access a variable through a pointer of an incompatible type
Page: MSC18-C. Be careful while handling sensitive data, such as passwords, in program code
Page: SIG35-C. Do not return from a computational exception signal handler
Page: MEM00-C. Allocate and free memory in the same module, at the same level of abstraction
Page: MEM04-C. Beware of zero-length allocations
Page: MSC07-C. Detect and remove dead code
Page: PRE32-C. Do not use preprocessor directives in invocations of function-like macros
Page: EXP43-C. Avoid undefined behavior when using restrict-qualified pointers
Page: DCL07-C. Include the appropriate type information in function declarators
Page: INT13-C. Use bitwise operators only on unsigned operands

Hierarchy

Parent Page
Page: EE. Analyzers

Labels

There are no labels assigned to this page.

Recent Changes

Time	Editor
May 03, 2024 14:13	Anirban Gangopadhyay	View Changes
Dec 01, 2023 16:31	Anirban Gangopadhyay	View Changes
Mar 22, 2023 14:26	Anirban Gangopadhyay	View Changes
Sep 26, 2022 16:07	Anirban Gangopadhyay	View Changes
Apr 26, 2022 11:49	Anirban Gangopadhyay

View Page History

Space shortcuts

Page tree