You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

This page was automatically generated and should not be edited.

The information on this page was provided by outside contributors and has not been verified by SEI CERT.

The table below can be re-ordered, by clicking column headers.

Tool Version: 2025.4.2

Checker

Guideline

PWD002 CON43-C. Do not allow data races in multithreaded code
PWD002 CON07-C. Ensure that compound operations on shared variables are atomic
PWD003 MEM35-C. Allocate sufficient memory for an object
PWD003 MSC15-C. Do not depend on undefined behavior
PWD004 ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
PWD005 ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
PWD005 MEM35-C. Allocate sufficient memory for an object
PWD006 EXP33-C. Do not read uninitialized memory
PWD006 ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
PWD006 MSC15-C. Do not depend on undefined behavior
PWD007 CON43-C. Do not allow data races in multithreaded code
PWD008 ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
PWD008 CON43-C. Do not allow data races in multithreaded code
PWD008 MSC15-C. Do not depend on undefined behavior
PWD010 CON43-C. Do not allow data races in multithreaded code
PWR001 DCL19-C. Minimize the scope of variables and functions
PWR002 DCL19-C. Minimize the scope of variables and functions
PWR007 DCL31-C. Declare identifiers before using them
PWR007 EXP37-C. Call functions with the correct number and type of arguments
PWR007 DCL07-C. Include the appropriate type information in function declarators
PWR008 DCL13-C. Declare function parameters that are pointers to values not changed by the function as const
PWR014 ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
PWR028 EXP08-C. Ensure pointer arithmetic is used correctly
PWR030 EXP08-C. Ensure pointer arithmetic is used correctly
PWR037 FLP34-C. Ensure that floating-point conversions are within range of the new type
PWR068 DCL31-C. Declare identifiers before using them
PWR068 EXP37-C. Call functions with the correct number and type of arguments
PWR068 DCL07-C. Include the appropriate type information in function declarators
PWR069 DCL23-C. Guarantee that mutually visible identifiers are unique
PWR070 API02-C. Functions that read or write to or from an array should take an argument to specify the source or target size
PWR071 FLP00-C. Understand the limitations of floating-point numbers
PWR075 MSC23-C. Beware of vendor-specific library and language differences
PWR079 EXP33-C. Do not read uninitialized memory
PWR079 EXP34-C. Do not dereference null pointers
PWR079 MEM01-C. Store a new value in pointers immediately after free()
PWR079 MSC15-C. Do not depend on undefined behavior
PWR080 EXP33-C. Do not read uninitialized memory
PWR080 EXP34-C. Do not dereference null pointers
PWR080 MEM01-C. Store a new value in pointers immediately after free()
PWR080 MSC15-C. Do not depend on undefined behavior
PWR081 EXP33-C. Do not read uninitialized memory
PWR081 EXP34-C. Do not dereference null pointers
PWR081 MEM01-C. Store a new value in pointers immediately after free()
PWR081 MSC15-C. Do not depend on undefined behavior
RMK016 FLP01-C. Take care in rearranging floating-point expressions
  • No labels