From 5ae1e02429f0aa082ec2e2b524c38031087c47bc Mon Sep 17 00:00:00 2001 From: eugenis Date: Thu, 27 Aug 2015 14:18:19 -0700 Subject: Re-enable memcmp interceptor for TSan. But make it not strict. This is roughly the same behavior as we had before the clang roll and the workaround in crbug.com/523384. BUG=523384 Review URL: https://codereview.chromium.org/1308023005 Cr-Commit-Position: refs/heads/master@{#345991} --- build/sanitizers/sanitizer_options.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'build/sanitizers/sanitizer_options.cc') diff --git a/build/sanitizers/sanitizer_options.cc b/build/sanitizers/sanitizer_options.cc index 235c0d5..342ab94 100644 --- a/build/sanitizers/sanitizer_options.cc +++ b/build/sanitizers/sanitizer_options.cc @@ -129,7 +129,7 @@ SANITIZER_HOOK_ATTRIBUTE const char *__asan_default_suppressions() { const char kTsanDefaultOptions[] = "detect_deadlocks=1 second_deadlock_stack=1 report_signal_unsafe=0 " "report_thread_leaks=0 print_suppressions=1 history_size=7 " - "intercept_memcmp=0 strip_path_prefix=Release/../../ "; + "strict_memcmp=0 strip_path_prefix=Release/../../ "; SANITIZER_HOOK_ATTRIBUTE const char *__tsan_default_options() { return kTsanDefaultOptions; -- cgit v1.1