Lines Matching defs:MemorySanitizer

2 MemorySanitizer
11 MemorySanitizer is a detector of uninitialized memory use. It consists of a
14 Typical slowdown introduced by MemorySanitizer is **3x**.
16 Here is a not comprehensive of list cases when MemorySanitizer will report an error:
32 The MemorySanitizer run-time library should be linked to the final
34 link step. When linking shared libraries, the MemorySanitizer run-time
36 with MemorySanitizer). To get a reasonable performance add ``-O1`` or
63 WARNING: MemorySanitizer: use-of-uninitialized-value
67 By default, MemorySanitizer exits on the first detected error. If you
75 whether MemorySanitizer is enabled. :ref:`\_\_has\_feature
82 // code that builds only under MemorySanitizer
89 Some code should not be checked by MemorySanitizer. One may use the function
91 particular function. MemorySanitizer may still instrument such functions to
107 MemorySanitizer supports ``src`` and ``fun`` entity types in
108 :doc:`SanitizerSpecialCaseList`, that can be used to relax MemorySanitizer
116 MemorySanitizer uses an external symbolizer to print files and line numbers in
125 MemorySanitizer can track origins of uninitialized values, similar to
147 WARNING: MemorySanitizer: use-of-uninitialized-value
159 By default, MemorySanitizer collects both allocation points and all
161 tracking has proved to be very useful for debugging MemorySanitizer
163 of the usual MemorySanitizer slowdown and increases memory overhead.
166 faster mode when MemorySanitizer collects only allocation points but
172 MemorySanitizer includes use-after-destruction detection. After invocation of
187 MemorySanitizer requires that all program code is instrumented. This
193 Full MemorySanitizer instrumentation is very difficult to achieve. To
194 make it easier, MemorySanitizer runtime library includes 70+
196 to run MemorySanitizer-instrumented programs linked with
198 MemorySanitizer-instrumented Clang compiler by linking it with
204 MemorySanitizer is a bug detection tool and its runtime is not meant to be
206 MemorySanitizer's runtime was not developed with security-sensitive
212 MemorySanitizer is supported on the following OS:
221 * MemorySanitizer uses 2x more real memory than a native run, 3x with
223 * MemorySanitizer maps (but not reserves) 64 Terabytes of virtual
231 * MemorySanitizer might be incompatible with position-independent executables
238 MemorySanitizer is known to work on large real-world programs
245 `<https://github.com/google/sanitizers/wiki/MemorySanitizer>`_