You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/sanitizers/asan-runtime.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ For convenience, the [AddressSanitizer interface header file](https://github.com
91
91
```
92
92
93
93
> [!NOTE]
94
-
> Manually poisoned memorymust be eventually unpoisoned. Otherwise, ASan may report false positives.
94
+
> If you manually poison memory, you must unpoison it before reuse. This is especially important for stack addresses (e.g. a stack local variable), which are frequently reused during program execution. You risk introducing `use-after-poison`false positives in manually poisoned stack addresses if you fail to unpoison them before their stack frame is removed.
95
95
96
96
## Alignment requirements for AddressSanitizer poisoning
0 commit comments