SecurityTest.NewOverflow failing under msan |
||
Issue descriptionhttps://build.chromium.org/p/chromium.memory.full/builders/Linux%20MSan%20Tests/builds/6022/steps/base_unittests/logs/SecurityTest.NewOverflow SecurityTest.NewOverflow (run #1): [ RUN ] SecurityTest.NewOverflow ==12431==WARNING: MemorySanitizer failed to allocate 0xffffffffffffffff bytes ==12431==MemorySanitizer's allocator is terminating the process instead of returning 0 ==12431==If you don't like this behavior set allocator_may_return_null=1 ==12431==Sanitizer CHECK failed: /b/build/slave/linux_upload_clang/build/src/third_party/llvm/compiler-rt/lib/sanitizer_common/sanitizer_allocator.cc:221 ((0)) != (0) (0, 0) The sanitizer runtime doesn't support new returning nullptr, see https://bugs.chromium.org/p/chromium/issues/detail?id=690271#c15 . The test is already disabled on ASan and TSan, just need to disable under MSan as well.
,
Mar 1 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bc1c10939650afc4ebf9da6282c8b568547ed12c commit bc1c10939650afc4ebf9da6282c8b568547ed12c Author: thakis <thakis@chromium.org> Date: Wed Mar 01 13:05:35 2017 Disable SecurityTest.NewOverflow under msan. See bug for more. BUG= 697420 TBR=siggi Review-Url: https://codereview.chromium.org/2722193002 Cr-Commit-Position: refs/heads/master@{#453923} [modify] https://crrev.com/bc1c10939650afc4ebf9da6282c8b568547ed12c/base/security_unittest.cc
,
Mar 1 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by thakis@chromium.org
, Mar 1 2017