Question 1

How to enable AddressSanitizer in GCC?

Accepted Answer

Use the -fsanitize=address flag during compilation and linking, e.g., gcc -fsanitize=address -g file.c -o program. This instruments the code to catch memory errors like buffer overflows at runtime.

Question 2

AddressSanitizer vs Valgrind, which is better?

Accepted Answer

AddressSanitizer is faster with lower overhead but requires recompilation, while Valgrind works on binaries without recompilation but is slower. Use ASan for continuous testing and Valgrind for deep, one-off analysis.

Question 3

Does ThreadSanitizer work with C++11 threads?

Accepted Answer

Yes, ThreadSanitizer supports modern C++ threading libraries, including C++11 std::thread, and can detect data races and deadlocks when enabled with -fsanitize=thread in compilers like Clang.

Question 4

Can I use sanitizers on Windows with Visual Studio?

Accepted Answer

Partially—AddressSanitizer is integrated into Visual Studio for C/C++, but other sanitizers like ThreadSanitizer may have limited support. Check Microsoft's documentation for specific flags and compatibility.

Question 5

How to reduce false positives from UndefinedBehaviorSanitizer?

Accepted Answer

Suppress specific checks using flags like -fno-sanitize=integer or annotate code with attributes such as __attribute__((no_sanitize("undefined"))). Tune options based on your codebase to avoid noise.

Question 6

Is MemorySanitizer effective for finding all uninitialized reads?

Accepted Answer

MemorySanitizer detects most uses of uninitialized memory but may miss cases in optimized code or with certain compiler settings. It requires all code to be instrumented and can add significant overhead.

sanitizer

What is sanitizer?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions