Report a CodeCheck rule issue (false positive / negative)¶
Rule-correctness questions are a recurring support theme — a check firing where it shouldn't (false positive), not firing where it should (false negative), or reporting the wrong severity/level for a standard.
Before reporting¶
- Confirm the CheckID and rule. Each violation shows a CheckID (visible in the GUI). Note it
and the exact standard/rule (e.g.
MISRA23_10.1). - Check your project accuracy. Many "false" results come from an inaccurate parse (missing includes/macros). Make sure the project is accurate first — Strict vs Fuzzy / accurate C/C++ — then re-run.
- Isolate a minimal example. A small snippet that reproduces the behavior is the fastest path to a fix.
Report it¶
Send SciTools:
- the CheckID and standard/rule,
- a minimal code snippet that reproduces it,
- what you expected vs. what CodeCheck reported (including severity/level if that's the issue),
- your Understand build (Help → About Understand).
Contact support ([email protected]). If you just need to accept a specific instance meanwhile, suppress it with a documented deviation.
Requesting a new / custom check¶
If the rule you need isn't covered, you can write a custom check or request one via support.