Checkers Deactivated in Polyspace as You Code Analysis
Polyspace® as You Code finds bugs and coding rule violations in the currently active file in your IDE. If finding an issue requires multiple source files, the analysis cannot flag the issue by design. To help you with the checkers selection strategy:
Checkers that typically produce most results in a multi-file context are completely deactivated in Polyspace as You Code.
Some coding standard checkers cover both single and multi-file issues. These checkers are not deactivated but have a reduced scope and show fewer issues in Polyspace as You Code compared to a full integration analysis.
You can detect these multi-file issues by running an integration analysis on your project by using Polyspace Bug Finder™ or Polyspace Bug Finder Server™.
Checkers and Coding Rule Deactivated in Polyspace as You Code
Checkers corresponding to these issues are deactivated in a Polyspace as You Code analysis. Even if you enable these checkers in your Polyspace
as You Code IDE extension settings (or using the option Checkers
activation file (-checkers-activation-file) (Polyspace Bug Finder)), they are internally
deactivated during analysis.
Deactivated Bug Finder Checkers
The Bug Finder checkers that are deactivated in a Polyspace as You Code analysis include:
Missing unlock(Polyspace Bug Finder)Missing lock(Polyspace Bug Finder)Blocking operation while holding lock(Polyspace Bug Finder)Data race(Polyspace Bug Finder)Data race on adjacent bit fields(Polyspace Bug Finder)Data race through standard library function call(Polyspace Bug Finder)Deadlock(Polyspace Bug Finder)Destruction of locked mutex(Polyspace Bug Finder)Join or detach of a joined or detached thread(Polyspace Bug Finder)Double lock(Polyspace Bug Finder)Double unlock(Polyspace Bug Finder)LDAP injection(Polyspace Bug Finder)Automatic or thread local variable escaping from a thread(Polyspace Bug Finder)Multiple mutexes used with same condition variable(Polyspace Bug Finder)Plain text password stored in file system(Polyspace Bug Finder)Incorrect use of test fixtures(Polyspace Bug Finder)Incorrect use of mocking API(Polyspace Bug Finder)Incorrect test registration or definition(Polyspace Bug Finder)Incorrect use of test setup/teardown API(Polyspace Bug Finder)Unsupported syntax used with test authoring API(Polyspace Bug Finder)Resource injection(Polyspace Bug Finder)Signal call in multithreaded program(Polyspace Bug Finder)Multiple threads waiting on same condition variable(Polyspace Bug Finder)SQL injection(Polyspace Bug Finder)Tainted source used with sensitive function(Polyspace Bug Finder)Thread-specific memory leak(Polyspace Bug Finder)Typedef mismatch(Polyspace Bug Finder)
Deactivated CERT C Rules
The CERT® C coding rules that are deactivated in a Polyspace as You Code analysis include:
CERT C: Rec. CON01-C(Polyspace Bug Finder)CERT C: Rec. CON05-C(Polyspace Bug Finder)CERT C: Rule CON30-C(Polyspace Bug Finder)CERT C: Rule CON31-C(Polyspace Bug Finder)CERT C: Rule CON32-C(Polyspace Bug Finder)CERT C: Rule CON33-C(Polyspace Bug Finder)CERT C: Rule CON34-C(Polyspace Bug Finder)CERT C: Rule CON35-C(Polyspace Bug Finder)CERT C: Rule CON37-C(Polyspace Bug Finder)CERT C: Rule CON38-C(Polyspace Bug Finder)CERT C: Rule CON39-C(Polyspace Bug Finder)CERT C: Rule CON43-C(Polyspace Bug Finder)CERT C: Rec. DCL15-C(Polyspace Bug Finder)CERT C: Rec. EXP12-C(Polyspace Bug Finder)CERT C: Rule POS48-C(Polyspace Bug Finder)CERT C: Rule POS49-C(Polyspace Bug Finder)CERT C: Rule POS50-C(Polyspace Bug Finder)CERT C: Rule POS51-C(Polyspace Bug Finder)CERT C: Rule POS52-C(Polyspace Bug Finder)CERT C: Rule POS53-C(Polyspace Bug Finder)
Deactivated CERT C++ Rules
The CERT C++ coding rules that are deactivated in a Polyspace as You Code analysis include:
CERT C++: CON33-C(Polyspace Bug Finder)CERT C++: CON37-C(Polyspace Bug Finder)CERT C++: CON43-C(Polyspace Bug Finder)CERT C++: CON50-CPP(Polyspace Bug Finder)CERT C++: CON51-CPP(Polyspace Bug Finder)CERT C++: CON52-CPP(Polyspace Bug Finder)CERT C++: CON53-CPP(Polyspace Bug Finder)CERT C++: CON55-CPP(Polyspace Bug Finder)CERT C++: CON56-CPP(Polyspace Bug Finder)CERT C++: EXP60-CPP(Polyspace Bug Finder)
Deactivated MISRA C:2004 and MISRA AC AGC Rules
The MISRA C™:2004 and MISRA™ AC AGC coding rules that are deactivated in a Polyspace as You Code analysis include:
5.1
8.10
8.9
Deactivated MISRA C:2012 Rules
The MISRA C:2012 coding rules that are deactivated in a Polyspace as You Code analysis include:
MISRA C:2012 Rule 2.3(Polyspace Bug Finder)MISRA C:2012 Rule 2.4(Polyspace Bug Finder)MISRA C:2012 Rule 2.5(Polyspace Bug Finder)MISRA C:2012 Rule 5.1(Polyspace Bug Finder)MISRA C:2012 Rule 5.8(Polyspace Bug Finder)MISRA C:2012 Rule 5.9(Polyspace Bug Finder)MISRA C:2012 Rule 8.6(Polyspace Bug Finder)MISRA C:2012 Rule 8.7(Polyspace Bug Finder)MISRA C:2012 Dir 4.13(Polyspace Bug Finder)MISRA C:2012 Dir 4.15(Polyspace Bug Finder)
Deactivated MISRA C:2023 Rules
The MISRA C:2012 coding rules that are deactivated in a Polyspace as You Code analysis include:
MISRA C:2023 Rule 2.3(Polyspace Bug Finder)MISRA C:2023 Rule 2.4(Polyspace Bug Finder)MISRA C:2023 Rule 2.5(Polyspace Bug Finder)MISRA C:2023 Rule 5.1(Polyspace Bug Finder)MISRA C:2023 Rule 5.8(Polyspace Bug Finder)MISRA C:2023 Rule 5.9(Polyspace Bug Finder)MISRA C:2023 Rule 8.6(Polyspace Bug Finder)MISRA C:2023 Rule 8.7(Polyspace Bug Finder)MISRA C:2023 Dir 4.13(Polyspace Bug Finder)MISRA C:2023 Dir 4.15(Polyspace Bug Finder)
Deactivated MISRA C++:2008 Rules
The MISRA C++:2008 coding rules that are deactivated in a Polyspace as You Code analysis include:
MISRA C++:2008 Rule 0-1-3(Polyspace Bug Finder)MISRA C++:2008 Rule 15-4-1(Polyspace Bug Finder)MISRA C++:2008 Rule 3-2-2(Polyspace Bug Finder)MISRA C++:2008 Rule 3-2-4(Polyspace Bug Finder)
Deactivated AUTOSAR C++14 Rules
The AUTOSAR C++14 coding rules that are deactivated in a Polyspace as You Code analysis include:
AUTOSAR C++14 Rule M0-1-3(Polyspace Bug Finder)AUTOSAR C++14 Rule M3-2-2(Polyspace Bug Finder)AUTOSAR C++14 Rule M3-2-4(Polyspace Bug Finder)
Deactivated CWE Rules
The CWE rules that are deactivated in a Polyspace as You Code analysis include:
Deactivated JSF C++ Coding Rules
The JSF® C++ coding rules that are deactivated in a Polyspace as You Code analysis include:
137
46
Related Topics
You can also select a web site from the following list:
Americas
- América Latina (Español)
- Canada (English)
- United States (English)
Europe
- Belgium (English)
- Denmark (English)
- Deutschland (Deutsch)
- España (Español)
- Finland (English)
- France (Français)
- Ireland (English)
- Italia (Italiano)
- Luxembourg (English)
- Netherlands (English)
- Norway (English)
- Österreich (Deutsch)
- Portugal (English)
- Sweden (English)
- Switzerland
- United Kingdom (English)