estelasupple01/4764223

The MemorySanitizer run-time library ought to be linked to the ultimate executable, so ensure to use clang (not ld) for the ultimate hyperlink step. When linking shared libraries, the MemorySanitizer run-time isn't linked, so -Wl,-z,defs may cause link errors (don’t use it with MemorySanitizer). To get a reasonable efficiency add -O1 or larger. To get meaningful stack traces in error messages add -fno-omit-frame-pointer. To get perfect stack traces you may need to disable inlining (just use -O1) and tail call elimination (-fno-optimize-sibling-calls). If a bug is detected, this system will print an error message to stderr and exit with a non-zero exit code. By default, MemorySanitizer exits on the first detected error. If you find the error report laborious to understand, attempt enabling origin tracking. In some cases one might have to execute totally different code depending on whether or not MemorySanitizer is enabled. Some code shouldn't be checked by MemorySanitizer. MemorySanitizer should still instrument such capabilities to keep away from false positives. As a result, it could introduce false positives and subsequently should be used with care, and provided that completely required