Invalid use of standard library integer routine
Wrong arguments to standard library function
Description
This defect occurs when you use invalid arguments with an integer function from the standard library. This defect picks up:
Character conversion functions (
toupper()
,tolower()
, and so on)Character check functions (
isalnum()
,isalpha()
,iscntrl()
,isdigit
, and so on)Integer division functions (
div()
,ldiv()
, and so on)Absolute value functions (
abs()
,labs()
, and so on)
Fix
The fix depends on the root cause of the defect. 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.
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
Extend this checker to check for defects caused by specific values and invalid use of functions from a custom library. For instance:
You might be using a custom library of mathematical functions. If a custom library function have the same domain and range as another function from the standard library, you can extend this checker to check the custom library function. See Extend Bug Finder Checkers for Standard Library Functions to Custom Libraries.
A default Bug Finder analysis might not raise a defect when the input values are unknown and only a subset of inputs can cause an issue. To check for defects caused by specific system input values, run a stricter Bug Finder analysis. See Extend Bug Finder Checkers to Find Defects from Specific System Input Values.
Examples
Result Information
Group: Numerical |
Language: C | C++ |
Default: On |
Command-Line Syntax: INT_STD_LIB |
Impact: High |
Version History
Introduced in R2013b
See Also
Find defects (-checkers)
| Invalid use of standard library floating point routine
| Invalid use of standard library memory routine
| Invalid use of standard library string routine
| Invalid use of standard library routine
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 Bug Finder Checkers for Standard Library Functions to Custom Libraries
- Extend Bug Finder Checkers to Find Defects from Specific System Input Values