Verification · Formal
Undefined-behaviour detection
Executes code under an interpreter or instrumentation that detects memory-safety and aliasing violations.
Sub-techniques
-
Interpreter-based checking
V1028.001Run tests under an interpreter that tracks every pointer (Miri).
-
Sanitizers
V1028.002Compile with address, thread or undefined-behaviour sanitizers and run the tests.
How to build it
- Run the unsafe-heavy test subset under the checker in CI.
- Add sanitizer builds as separate matrix entries.
- Treat every report as a bug; there are no false positives to baseline.
Signals in a repository
- cargo miri test or -Zsanitizer flags in workflows.
- ASAN_OPTIONS or -fsanitize in build scripts.