• clemensh's avatar
    [wasm] Make wasm info available on the stack trace · a4cd1eef
    clemensh authored
    This changes different locations to extract the reference to the wasm
    object and the function index from the stack trace, and make it
    available through all the APIs which process stack traces.
    The javascript CallSite object now has the new methods isWasm(),
    getWasmObject() and getWasmFunctionIndex(); the byte offset is
    available via getPosition().
    
    Function names of wasm frames should be fully functional with this
    commit, position information works reliably for calls, but not for
    traps like unreachable or out-of-bounds accesses.
    
    R=titzer@chromium.org, yangguo@chromium.org
    
    Review-Url: https://codereview.chromium.org/1909353002
    Cr-Commit-Position: refs/heads/master@{#36067}
    a4cd1eef
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
fuzzer 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...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
ignition.gyp Loading commit data...
ignition.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...