[PATCH] D12914: Updating docs for poison-in-dtor.
Naomi Musgrave via llvm-commits
llvm-commits at lists.llvm.org
Wed Sep 16 16:54:19 PDT 2015
nmusgrave updated this revision to Diff 34941.
nmusgrave added a comment.
- Revise doc description of use-after-dtor.
http://reviews.llvm.org/D12914
Files:
docs/UsersManual.rst
Index: docs/UsersManual.rst
===================================================================
--- docs/UsersManual.rst
+++ docs/UsersManual.rst
@@ -1065,6 +1065,16 @@
order of memory stores the uninitialized value went
through. This mode may use extra memory in programs that copy
uninitialized memory a lot.
+ - ``-fsanitize-memory-use-after-dtor``: Enables use-after-destruction
+ detection in MemorySanitizer. After invocation of the destructor,
+ the object is considered no longer accessible. Facilitates the
+ detection of use-after-destroy bugs.
+
+ Setting the MSAN_OPTIONS=poison_in_dtor=1 enables the poisoning of
+ memory at runtime. Any subsequent access to the destroyed object
+ fails at runtime. This feature is still experimental, but this
+ environment variable must be set to 1 in order for the above flag
+ to have any effect.
The ``-fsanitize=`` argument must also be provided when linking, in
order to link to the appropriate runtime library. When using
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D12914.34941.patch
Type: text/x-patch
Size: 1051 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150916/80ef61b8/attachment.bin>
More information about the llvm-commits
mailing list