[infra] Remove "null" check from UBSan options. (#674)

There is not much value for us from this particular check:
- UBSan's "null" reports leading to real crashes are reported with ASan as well.
- Potential null references are not real crashes and might be considered
  as false positives, though it seems to be UB as per the standard.
This commit is contained in:
Max Moroz 2017-06-12 10:46:53 -07:00 committed by Abhishek Arya
parent 1353edfc44
commit 3cee68fa11
1 changed files with 1 additions and 1 deletions

View File

@ -20,7 +20,7 @@ RUN apt-get install -y git subversion jq python3 zip make libunwind8-dev binutil
# Default build flags for various sanitizers.
ENV SANITIZER_FLAGS_address "-fsanitize=address -fsanitize-address-use-after-scope"
ENV SANITIZER_FLAGS_undefined "-fsanitize=bool,array-bounds,float-divide-by-zero,function,integer-divide-by-zero,null,return,shift,signed-integer-overflow,vla-bound,vptr -fno-sanitize-recover=undefined"
ENV SANITIZER_FLAGS_undefined "-fsanitize=bool,array-bounds,float-divide-by-zero,function,integer-divide-by-zero,return,shift,signed-integer-overflow,vla-bound,vptr -fno-sanitize-recover=undefined"
ENV SANITIZER_FLAGS_memory "-fsanitize=memory -fsanitize-memory-track-origins"
# Default build flags for coverage.