address-sanitizer
Audited by Runlayer on Feb 26, 2026
Malicious tool definition detected
- **Stack trace**: Where the error occurred - **Allocation/deallocation traces**: Where memory was allocated/freed - **Memory map**: Shadow memory state around the error Example ASan report: ``` ==12345==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60300000eff4 at pc 0x00000048e6a3 READ of size 4 at 0x60300000eff4 thread T0 #0 0x48e6a2 in main /path/to/file.c:42 ``` ### Combining Sanitizers ASan can be combined with other sanitizers for comprehensive detection: ```bash clang -fsani
Description: not initialized" | Wrong linking order or missing runtime | Ensure `-fsanitize=address` used in both compile and link | | Leak reports clutter output | LeakSanitizer enabled by default | Set `ASAN_OPTIONS=detect_leaks=0` | | Poor performance (>4x slowdown) | Debug mode or unoptimized build | Compile with `-O2` or `-O3` alongside `-fsanitize=address` | | ASan not detecting obvious bugs | Binary not instrumented | Check with `ASAN_OPTIONS=verbosity=1` that ASan prints startup info | |