[PATCH] D44404: [ASan] Report proper ASan error on allocator failures instead of CHECK(0)-ing

[Aleksey Shlyapnikov via Phabricator via llvm-commits]

alekseyshl created this revision.
alekseyshl added a reviewer: eugenis.
Herald added subscribers: Sanitizers, delcypher, kubamracek.

Currently many allocator specific errors (OOM, for example) are reported as
a text message and CHECK(0) termination, not stack, no details, not too
helpful nor informative. To improve the situation, ASan detailed errors were
defined and reported under the appropriate conditions.

Issue: https://github.com/google/sanitizers/issues/887


Repository:
  rCRT Compiler Runtime

https://reviews.llvm.org/D44404

Files:
  lib/asan/asan_allocator.cc
  lib/asan/asan_errors.cc
  lib/asan/asan_errors.h
  lib/asan/asan_new_delete.cc
  lib/asan/asan_report.cc
  lib/asan/asan_report.h
  lib/sanitizer_common/sanitizer_allocator.cc
  lib/sanitizer_common/sanitizer_allocator.h
  test/asan/TestCases/Linux/aligned_alloc-alignment.cc
  test/asan/TestCases/Linux/allocator_oom_test.cc
  test/asan/TestCases/Linux/pvalloc-overflow.cc
  test/asan/TestCases/Posix/posix_memalign-alignment.cc
  test/asan/TestCases/Windows/oom.cc
  test/asan/TestCases/allocator_returns_null.cc
  test/asan/TestCases/calloc-overflow.cc
  test/asan/TestCases/malloc-size-too-big.cc
  test/sanitizer_common/TestCases/Linux/soft_rss_limit_mb_test.cc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: D44404.138109.patch
Type: text/x-patch
Size: 27457 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20180312/9ff841f7/attachment.bin>