[PATCH] [asancov] Write coverage directly to a memory-mapped file
Evgeniy Stepanov
eugenis at google.com
Thu May 22 06:13:20 PDT 2014
Hi kcc, dvyukov,
This way does not require a __sanitizer_cov_dump() call. That's important on Android, where apps can be killed at arbitrary time.
We write raw PCs to disk instead of module offsets; we also write memory layout to a separate file. This increases dump size by the factor of 2 on 64-bit systems.
http://reviews.llvm.org/D3874
Files:
lib/asan/asan_interceptors.cc
lib/sanitizer_common/CMakeLists.txt
lib/sanitizer_common/sanitizer_common.h
lib/sanitizer_common/sanitizer_common_interceptors.inc
lib/sanitizer_common/sanitizer_coverage.cc
lib/sanitizer_common/sanitizer_coverage_direct.cc
lib/sanitizer_common/sanitizer_coverage_direct.h
lib/sanitizer_common/sanitizer_flags.cc
lib/sanitizer_common/sanitizer_flags.h
lib/sanitizer_common/sanitizer_libc.h
lib/sanitizer_common/sanitizer_linux.cc
lib/sanitizer_common/sanitizer_platform_interceptors.h
lib/sanitizer_common/sanitizer_posix.cc
lib/sanitizer_common/scripts/sancov.py
lib/tsan/rtl/tsan_interceptors.cc
test/asan/TestCases/Linux/coverage-direct-large.cc
test/asan/TestCases/Linux/coverage-direct.cc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D3874.9693.patch
Type: text/x-patch
Size: 22584 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140522/b1ef9659/attachment.bin>
More information about the llvm-commits
mailing list