address-sanitizer

# AddressSanitizer ## Contract | Field | Bound contract | |---|---| | Trigger | User needs to build or run native code with ASan, interpret an ASan report, or debug a memory-corruption failure. | | Authority | Reversible local: writes only the instrumented build artifacts and test invocations named by the user; rollback is discarding the instrumented binary and rebuilding without `-fsanitize=address`. No remote mutation. | | Side effect | Instrumented native build and test process under the target project directory. | | Done | When building or running: the target is instrumented, exercised, and any reported memory error is explained with a reproducible location. When interpreting an existing report: the error type, faulting source location, and allocation/deallocation sites are extracted from the report and mapped to a root cause, without requiring a fresh instrumented run. | ## Inputs Required when building or running: the native source or build target to instrument (C/C++ source, Rust crate with unsafe blocks or FFI, or an existing fuzz harness) and the command that exercises it. Required when interpreting a report: a specific ASan report file or captured ASan output. Optional: a preferred sanitizer combination, or a fuzzer in use (libFuzzer, AFL++, cargo-fuzz, honggfuzz). When interpreting a report, the build target and exercise command are also optional and used only to confirm the root cause against source. ## Procedure 1. Determine the invocation mode. If the us...