• Clemens Backes's avatar
    [wasm] Disallow late enabling of trap handlers · bcb0a7c5
    Clemens Backes authored
    It's dangerous if trap handlers are enabled after we already used the
    information whether they are enabled or not.
    This CL checks for such misbehaviour by remembering whether
    {IsTrapHandlerEnabled} was already called, and disallowing
    {EnableTrapHandler} afterwards. Also, calling {EnableTrapHandler}
    multiple times is disallowed now.
    
    The trap handler tests are changed to only enable trap handlers once,
    and to do that before allocating wasm memory or generating code.
    
    R=ahaas@chromium.org
    
    Bug: v8:11017
    Change-Id: Ib2256bb8435efd914c12769cedd4a0051052aeef
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2494935Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
    Commit-Queue: Clemens Backes <clemensb@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#70750}
    bcb0a7c5
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
debugging Loading commit data...
fuzzer Loading commit data...
fuzzilli Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
test262 Loading commit data...
torque Loading commit data...
unittests Loading commit data...
wasm-api-tests Loading commit data...
wasm-js Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
OWNERS Loading commit data...