[PATCH] D124058: [msan] Update Use-after-destruction documentation
Vitaly Buka via Phabricator via cfe-commits
cfe-commits at lists.llvm.org
Thu Apr 21 14:02:31 PDT 2022
This revision was automatically updated to reflect the committed changes.
Closed by commit rGb580c0e01982: [msan] Update Use-after-destruction documentation (authored by vitalybuka).
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D124058/new/
https://reviews.llvm.org/D124058
Files:
clang/docs/MemorySanitizer.rst
Index: clang/docs/MemorySanitizer.rst
===================================================================
--- clang/docs/MemorySanitizer.rst
+++ clang/docs/MemorySanitizer.rst
@@ -162,17 +162,16 @@
Use-after-destruction detection
===============================
-You can enable experimental use-after-destruction detection in MemorySanitizer.
-After invocation of the destructor, the object will be considered no longer
-readable, and using underlying memory will lead to error reports in runtime.
-Refer to the standard for `lifetime <https://eel.is/c++draft/basic.life#1>`_ definition.
+MemorySanitizer includes use-after-destruction detection. After invocation of
+the destructor, the object will be considered no longer readable, and using
+underlying memory will lead to error reports in runtime. Refer to the standard
+for `lifetime <https://eel.is/c++draft/basic.life#1>`_ definition.
-This feature is still experimental, in order to enable it at runtime you need
-to:
+This feature can be disabled with either:
-#. Pass addition Clang option ``-fsanitize-memory-use-after-dtor`` during
+#. Pass addition Clang option ``-fno-sanitize-memory-use-after-dtor`` during
compilation.
-#. Set environment variable `MSAN_OPTIONS=poison_in_dtor=1` before running
+#. Set environment variable `MSAN_OPTIONS=poison_in_dtor=0` before running
the program.
Handling external code
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D124058.424284.patch
Type: text/x-patch
Size: 1392 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20220421/d6fb97fa/attachment.bin>
More information about the cfe-commits
mailing list