Non-initialized variable
Variable not initialized before use
Description
This defect occurs when a variable is not initialized before its value is read.
Risk
Unless a variable is explicitly initialized, the variable value is unpredictable. You cannot rely on the variable having a specific value.
Fix
The fix depends on the root cause of the defect. For instance, you assigned a value to the variable but the assignment is unreachable or you assigned a value to the variable in one of two branches of a conditional statement. Fix the unreachable code or missing assignment.
Often the result details (or source code tooltips in Polyspace as You Code) show a sequence of events that led to the defect. You can implement the fix on any event in the sequence. If the result details do not show this event history, you can search for previous references of variables relevant to the defect using right-click options in the source code and find related events. See also Interpret Bug Finder Results in Polyspace Desktop User Interface or Interpret Bug Finder Results in Polyspace Access Web Interface (Polyspace Access).
See examples of fixes below. It is a good practice to initialize a variable at declaration.
If you do not want to fix the issue, add comments to your result or code to avoid another review. See:
Address Results in Polyspace User Interface Through Bug Fixes or Justifications if you review results in the Polyspace user interface.
Address Results in Polyspace Access Through Bug Fixes or Justifications (Polyspace Access) if you review results in a web browser.
Annotate Code and Hide Known or Acceptable Results if you review results in an IDE.
Extend Checker
You can extend the checker in the following ways:
Polyspace® does not flag passing pointers to noninitialized variables to functions. To detect noninitialized variables that are passed to functions by pointers, extend the checker by using the option
-code-behavior-specification
. See Extend Checkers for Initialization to Check Function Arguments Passed by Pointers.If a variable in your code is non-initialized only for certain system input values, you can see one possible combination of input values causing the defect. See Extend Bug Finder Checkers to Find Defects from Specific System Input Values.
Examples
Result Information
Group: Data flow |
Language: C | C++ |
Default: On |
Command-Line Syntax: NON_INIT_VAR |
Impact: High |
Version History
Introduced in R2013b
See Also
Find defects (-checkers)
| Non-initialized pointer
Topics
- Interpret Bug Finder Results in Polyspace Desktop User Interface
- Interpret Bug Finder Results in Polyspace Access Web Interface (Polyspace Access)
- Address Results in Polyspace User Interface Through Bug Fixes or Justifications
- Address Results in Polyspace Access Through Bug Fixes or Justifications (Polyspace Access)
- Extend Checkers for Initialization to Check Function Arguments Passed by Pointers