Chrome Version: tip
OS: Linux x86-64
What steps will reproduce the problem?
(1) Build chrome with use_cfi_diag=true (this option is enabled on the Linux CFI trybot.)
(2) Chrome will not run unit tests that test CFI (in base/tools_sanity_unittest.cc) since CFI_ENFORCEMENT is not set for use_cfi_diag=true. Even if they did run it would not have caught that CFI was broken in that configuration because the tests are too limited: they would trigger the all-vtables check but not test a failure due to a valid-but-incorrect vtable.
Expected behavior: tests that thoroughly verify that cfi-vcall and both cfi-unrelated-cast and cfi-derived-cast are properly detected should run by default. This is currently blocked on rolling clang to pick-up the CFI fixes for use_cfi_diag=true.
Comment 1 by bugdroid1@chromium.org
, Aug 15 2017