summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoreugenis <eugenis@chromium.org>2015-08-27 14:18:19 -0700
committerCommit bot <commit-bot@chromium.org>2015-08-27 21:19:02 +0000
commit5ae1e02429f0aa082ec2e2b524c38031087c47bc (patch)
treeb2ab0b28ca1435fbb702a6d698128b49cf413466
parentb03c07d4d23188902d42d60e74b160f8a6aba38a (diff)
downloadchromium_src-5ae1e02429f0aa082ec2e2b524c38031087c47bc.zip
chromium_src-5ae1e02429f0aa082ec2e2b524c38031087c47bc.tar.gz
chromium_src-5ae1e02429f0aa082ec2e2b524c38031087c47bc.tar.bz2
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}
-rw-r--r--build/sanitizers/sanitizer_options.cc2
1 files changed, 1 insertions, 1 deletions
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;