New issue
Advanced search Search tips

Issue 808217 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

base::no_destructor usage caused Linux CFI build failure.

Project Member Reported by bbudge@chromium.org, Feb 1 2018

Issue description

I'm not sure why this failed. Perhaps I'm using it wrong?

Usage was:
https://chromium-review.googlesource.com/c/chromium/src/+/896959/10/gin/v8_platform.cc

Error:
https://ci.chromium.org/buildbot/chromium.memory/Linux%20CFI/5604

[19881/22628] ACTION //tools/v8_context_snapshot:generate_v8_context_snapshot(//build/toolchain/linux:clang_x64)
FAILED: v8_context_snapshot.bin 
python ../../build/gn_run_binary.py ./v8_context_snapshot_generator --output_file=v8_context_snapshot.bin
../../base/no_destructor.h:64:21: runtime error: control flow integrity check for type 'gin::(anonymous namespace)::PageAllocator' failed during cast to unrelated type (vtable address 0x000000000000)
0x000000000000: note: invalid vtable
<memory cannot be printed>
./v8_context_snapshot_generator failed with exit code 1


 
Hmm. That is surprising. Is it possible to get an actual stack trace of the code that was running when this happened?
Another possible clue - Clusterfuzz detected a bad cast:

https://bugs.chromium.org/p/chromium/issues/detail?id=808320#c2

Sign in to add a comment