Can't enable DCHECK without disabling this in all fuzzing builds |
|||
Issue descriptionWe use a ton of release builds with memory instrumented tools. After you last enabled it, it just broke everything on ClusterFuzz. Reason being we don't expect startup crashes with simple tests, so existing more important crash testcases just start getting closed because they will start crashing on completely unrelated stacks. We need to add explicit hooks to disable this in fuzzing release builds All Sanitizer Builds (ASAN, MSAN, UBSAN, UBSAN VPTR, CFI, TSAN) SYZYASAN builds
,
Jul 17 2017
,
Mar 19 2018
This was strongly noted in 722827, if we try this again it will be based on is_component_build not !is_official_build |
|||
►
Sign in to add a comment |
|||
Comment 1 by gab@chromium.org
, May 25 2017