• jochen's avatar
    Do an access check before compiling code via eval() · 2f8d4f44
    jochen authored
    Similarly to how we check whether the entered context has access to the target
    context when invoking the function constructor, we should check the involved
    contexts before invoking eval().
    
    I forgot to add this in the initial CL that adds the check for the function
    constructor. Move the code to a common location, and use it for the GlobalEval
    builtin as well.
    
    BUG=chromium:541703
    R=verwaest@chromium.org
    
    Review-Url: https://codereview.chromium.org/2199343002
    Cr-Commit-Position: refs/heads/master@{#38277}
    2f8d4f44
Name
Last commit
Last update
benchmarks Loading commit data...
build_overrides Loading commit data...
docs Loading commit data...
gni Loading commit data...
gypfiles Loading commit data...
include Loading commit data...
infra Loading commit data...
samples Loading commit data...
src Loading commit data...
test Loading commit data...
testing Loading commit data...
third_party/binutils Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.gn Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
CODE_OF_CONDUCT.md Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.fdlibm Loading commit data...
LICENSE.strongtalk Loading commit data...
LICENSE.v8 Loading commit data...
LICENSE.valgrind Loading commit data...
Makefile Loading commit data...
Makefile.android Loading commit data...
OWNERS Loading commit data...
PRESUBMIT.py Loading commit data...
README.md Loading commit data...
WATCHLISTS Loading commit data...
codereview.settings Loading commit data...
snapshot_toolchain.gni Loading commit data...