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

Side by Side Diff: build/config/sanitizers/sanitizers.gni

Issue 1832213002: [libfuzzer] separate libfuzzer ubsan configuration and ubsan build config setup. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 8 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
OLDNEW
1 # Copyright 2015 The Chromium Authors. All rights reserved. 1 # Copyright 2015 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 declare_args() { 5 declare_args() {
6 # Compile for Address Sanitizer to find memory bugs. 6 # Compile for Address Sanitizer to find memory bugs.
7 is_asan = false 7 is_asan = false
8 8
9 # Compile for Leak Sanitizer to find leaks. 9 # Compile for Leak Sanitizer to find leaks.
10 is_lsan = false 10 is_lsan = false
(...skipping 31 matching lines...) Expand 10 before | Expand all | Expand 10 after
42 is_cfi = false 42 is_cfi = false
43 43
44 # By default, Control Flow Integrity will crash the program if it detects a 44 # By default, Control Flow Integrity will crash the program if it detects a
45 # violation. Set this to true to print detailed diagnostics instead. 45 # violation. Set this to true to print detailed diagnostics instead.
46 use_cfi_diag = false 46 use_cfi_diag = false
47 47
48 # Compile for fuzzing with LLVM LibFuzzer. 48 # Compile for fuzzing with LLVM LibFuzzer.
49 # See http://www.chromium.org/developers/testing/libfuzzer 49 # See http://www.chromium.org/developers/testing/libfuzzer
50 use_libfuzzer = false 50 use_libfuzzer = false
51 51
52 # Separate configuration for libfuzzer ubsan build. Used to deploy ubsan
53 # gradually. Eventually should catch up with is_ubsan and should be removed.
inferno 2016/03/25 20:57:55 Can you fix the comment to indicate this is a flag
aizatsky 2016/03/25 21:02:45 Done.
54 is_libfuzzer_ubsan = false
55
52 # Compile for fuzzing with Dr. Fuzz 56 # Compile for fuzzing with Dr. Fuzz
53 # See http://www.chromium.org/developers/testing/dr-fuzz 57 # See http://www.chromium.org/developers/testing/dr-fuzz
54 use_drfuzz = false 58 use_drfuzz = false
55 59
56 # Helper variable for testing builds with disabled libfuzzer. 60 # Helper variable for testing builds with disabled libfuzzer.
57 # Not for client use. 61 # Not for client use.
58 disable_libfuzzer = false 62 disable_libfuzzer = false
59 } 63 }
60 64
61 # Args that are in turn dependent on other args must be in a separate 65 # Args that are in turn dependent on other args must be in a separate
(...skipping 28 matching lines...) Expand all
90 # If you find a use-case where you want to compile a sanitizer in debug mode 94 # If you find a use-case where you want to compile a sanitizer in debug mode
91 # and have verified it works, ask brettw and we can consider removing it from 95 # and have verified it works, ask brettw and we can consider removing it from
92 # this condition. We may also be able to find another way to enable your case 96 # this condition. We may also be able to find another way to enable your case
93 # without having people accidentally get broken builds by compiling an 97 # without having people accidentally get broken builds by compiling an
94 # unsupported or unadvisable configurations. 98 # unsupported or unadvisable configurations.
95 # 99 #
96 # For one-off testing, just comment this assertion out. 100 # For one-off testing, just comment this assertion out.
97 assert( 101 assert(
98 !is_debug || !(is_msan || is_lsan || is_tsan || is_ubsan || is_ubsan_vptr), 102 !is_debug || !(is_msan || is_lsan || is_tsan || is_ubsan || is_ubsan_vptr),
99 "Sanitizers should generally be used in release (set is_debug=false).") 103 "Sanitizers should generally be used in release (set is_debug=false).")
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698