diff options
| author | George Burgess IV <gbiv@google.com> | 2017-09-12 16:54:53 -0700 |
|---|---|---|
| committer | George Burgess IV <gbiv@google.com> | 2017-09-12 17:01:20 -0700 |
| commit | 180e5e7021d17176bf2f5f110970e58cb19d6310 (patch) | |
| tree | 2bfa06335390fe0ceb35a31bc05712ab9c790288 /trusty/coverage/coverage_test.cpp | |
| parent | cfadedb1391f82a25bc0209aaa2e069875657776 (diff) | |
Fix static analyzer warnings
The static analyzer was complaining that we were potentially leaking
memory here (in `ASSERT_NE(ptr, nullptr)` after `new (char)`). This
wasn't correct, but it's also not possible for `new` to return nullptr
without std::nothrow.
In any case, swap to direct calls to `::operator new`, since it looks
like this test explicitly wants calls to `::operator new` to be emitted
(which the C++ standard doesn't guarantee for all `new` expressions).
Bug: 27101951
Test: mma; static analyzer warnings are gone. Also ran
memunreachable_test on marlin; no failures.
Change-Id: Ia740e41079f263040da978ba1ccc71c9c39f53fd
Diffstat (limited to 'trusty/coverage/coverage_test.cpp')
0 files changed, 0 insertions, 0 deletions