Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(323)

Side by Side Diff: build/common.gypi

Issue 349433005: Switch to tools/memory/tsan_v2/ignores.txt when building with ThreadSanitizer v2 (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 6 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | tools/valgrind/tsan_v2/ignores.txt » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Copyright (c) 2012 The Chromium Authors. All rights reserved. 1 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
2 # Use of this source code is governed by a BSD-style license that can be 2 # Use of this source code is governed by a BSD-style license that can be
3 # found in the LICENSE file. 3 # found in the LICENSE file.
4 4
5 # IMPORTANT: 5 # IMPORTANT:
6 # Please don't directly include this file if you are building via gyp_chromium, 6 # Please don't directly include this file if you are building via gyp_chromium,
7 # since gyp_chromium is automatically forcing its inclusion. 7 # since gyp_chromium is automatically forcing its inclusion.
8 { 8 {
9 # Variables expected to be overriden on the GYP command line (-D) or by 9 # Variables expected to be overriden on the GYP command line (-D) or by
10 # ~/.gyp/include.gypi. 10 # ~/.gyp/include.gypi.
(...skipping 356 matching lines...) Expand 10 before | Expand all | Expand 10 after
367 367
368 # Enable building with LSan (Clang's -fsanitize=leak option). 368 # Enable building with LSan (Clang's -fsanitize=leak option).
369 # -fsanitize=leak only works with clang, but lsan=1 implies clang=1 369 # -fsanitize=leak only works with clang, but lsan=1 implies clang=1
370 # See https://sites.google.com/a/chromium.org/dev/developers/testing/leaks anitizer 370 # See https://sites.google.com/a/chromium.org/dev/developers/testing/leaks anitizer
371 'lsan%': 0, 371 'lsan%': 0,
372 372
373 # Enable building with TSan (Clang's -fsanitize=thread option). 373 # Enable building with TSan (Clang's -fsanitize=thread option).
374 # -fsanitize=thread only works with clang, but tsan=1 implies clang=1 374 # -fsanitize=thread only works with clang, but tsan=1 implies clang=1
375 # See http://clang.llvm.org/docs/ThreadSanitizer.html 375 # See http://clang.llvm.org/docs/ThreadSanitizer.html
376 'tsan%': 0, 376 'tsan%': 0,
377 'tsan_blacklist%': '<(PRODUCT_DIR)/../../tools/valgrind/tsan_v2/ignores.tx t', 377 'tsan_blacklist%': '<(PRODUCT_DIR)/../../tools/memory/tsan_v2/ignores.txt' ,
378 378
379 # Enable building with MSan (Clang's -fsanitize=memory option). 379 # Enable building with MSan (Clang's -fsanitize=memory option).
380 # MemorySanitizer only works with clang, but msan=1 implies clang=1 380 # MemorySanitizer only works with clang, but msan=1 implies clang=1
381 # See http://clang.llvm.org/docs/MemorySanitizer.html 381 # See http://clang.llvm.org/docs/MemorySanitizer.html
382 'msan%': 0, 382 'msan%': 0,
383 'msan_blacklist%': '<(PRODUCT_DIR)/../../tools/msan/blacklist.txt', 383 'msan_blacklist%': '<(PRODUCT_DIR)/../../tools/msan/blacklist.txt',
384 # Track where uninitialized memory originates from. From fastest to 384 # Track where uninitialized memory originates from. From fastest to
385 # slowest: 0 - no tracking, 1 - track only the initial allocation site, 2 385 # slowest: 0 - no tracking, 1 - track only the initial allocation site, 2
386 # - track the chain of stores leading from allocation site to use site. 386 # - track the chain of stores leading from allocation site to use site.
387 'msan_track_origins%': 1, 387 'msan_track_origins%': 1,
(...skipping 5123 matching lines...) Expand 10 before | Expand all | Expand 10 after
5511 # settings in target dicts. SYMROOT is a special case, because many other 5511 # settings in target dicts. SYMROOT is a special case, because many other
5512 # Xcode variables depend on it, including variables such as 5512 # Xcode variables depend on it, including variables such as
5513 # PROJECT_DERIVED_FILE_DIR. When a source group corresponding to something 5513 # PROJECT_DERIVED_FILE_DIR. When a source group corresponding to something
5514 # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the 5514 # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the
5515 # files to appear (when present) in the UI as actual files and not red 5515 # files to appear (when present) in the UI as actual files and not red
5516 # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR, 5516 # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR,
5517 # and therefore SYMROOT, needs to be set at the project level. 5517 # and therefore SYMROOT, needs to be set at the project level.
5518 'SYMROOT': '<(DEPTH)/xcodebuild', 5518 'SYMROOT': '<(DEPTH)/xcodebuild',
5519 }, 5519 },
5520 } 5520 }
OLDNEW
« no previous file with comments | « no previous file | tools/valgrind/tsan_v2/ignores.txt » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698