I guess you might have already figured that out in a Google-internal
chat, but msan actually requires that the used libc++ is also compiled
with msan enabled. Totally forgot that this is a requirement for msan
(sorry).
I don't think there is a public LLDB msan bot (?), but you can
probably try
Not sure if there is a public builder with sanitizer enabled, but
compiling LLDB with -DLLVM_USE_SANITIZER=Memory and then doing ninja
check-lldb should be enough to reproduce this IIUC.
Am Mo., 6. Sept. 2021 um 12:17 Uhr schrieb Andy Yankovsky via
lldb-commits :
>
> Thanks for flagging this!
Thanks for flagging this! Adding the author of the change.
Does it fail somewhere on the llvm builders? Is there an easy way to
reproduce this locally?
On Thu, 2 Sept 2021 at 01:53, Richard Smith wrote:
> The new test fails under MSan:
>
> Uninitialized bytes in __interceptor_write at offset
The new test fails under MSan:
Uninitialized bytes in __interceptor_write at offset 2 inside
[0x7fb1f42ed000, 18438530)
==3871==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x55f5706515d9 in RetryAfterSignal
llvm-project/llvm/include/llvm/Support/Errno.h:38:11
#1 0x55f5706515d9
Author: Andrej Korman
Date: 2021-09-01T15:14:29+02:00
New Revision: eee687a66d76bf0b6e3746f7b8d09b0d871bff27
URL:
https://github.com/llvm/llvm-project/commit/eee687a66d76bf0b6e3746f7b8d09b0d871bff27
DIFF:
https://github.com/llvm/llvm-project/commit/eee687a66d76bf0b6e3746f7b8d09b0d871bff27.diff
