address-sanitizer

Compile and link with the -fsanitize=address flag using Clang or GCC, adding -g for detailed stack traces. For libFuzzer, combine it as -fsanitize=fuzzer,address and run with -rss_limit_mb=0 to allow ASan's virtual memory usage.

Set the AFL_USE_ASAN=1 environment variable when compiling with afl-clang-fast++, which automatically adds the proper instrumentation flags. Then run afl-fuzz with -m none to disable the memory limit that would otherwise kill ASan-instrumented processes.

ASan has full support and best performance on Linux. macOS has limited support with some features unavailable, while Windows support is experimental and not recommended for production fuzzing workflows.

ASan requires approximately 20TB of virtual memory for its shadow memory mapping, which exceeds default fuzzer memory limits. Disable the limits using -rss_limit_mb=0 for libFuzzer or -m none for AFL++.

No, ASan should only be used during testing and fuzzing. It introduces a 2-4x performance slowdown and can actually reduce security in production by exposing additional attack surface through its runtime instrumentation.

Yes, ASan can be combined with UndefinedBehaviorSanitizer using -fsanitize=address,undefined for comprehensive detection of both memory errors and undefined behavior. This combination is commonly used in fuzzing setups.