diff options
| author | Kostya Serebryany <kcc@google.com> | 2012-10-30 05:07:05 +0000 |
|---|---|---|
| committer | Kostya Serebryany <kcc@google.com> | 2012-10-30 05:07:05 +0000 |
| commit | ecf7cc18ced8a384ef373e7f04ba3b70ea2fd5a7 (patch) | |
| tree | d35ec42cdb335e816fdc10372f6a39e1de849fda | |
| parent | 4a131e1c6360419ceabdae80175ccb43d0ca31ee (diff) | |
[asan docs] explain why asan exits on the first error
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@167004 91177308-0d34-0410-b5e6-96231b3b80d8
| -rw-r--r-- | docs/AddressSanitizer.html | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/AddressSanitizer.html b/docs/AddressSanitizer.html index d60cdd9d35..4939079917 100644 --- a/docs/AddressSanitizer.html +++ b/docs/AddressSanitizer.html @@ -105,6 +105,13 @@ previously allocated by thread T0 here: ==9442== ABORTING </pre> +AddressSanitizer exits on the first detected error. This is by design. +One reason: it makes the generated code smaller and faster (both by ~5%). +Another reason: this makes fixing bugs unavoidable. With Valgrind, it is often +the case that users treat Valgrind warnings as false positives +(which they are not) and don't fix them. + + <h3 id="has_feature">__has_feature(address_sanitizer)</h3> In some cases one may need to execute different code depending on whether AddressSanitizer is enabled. |