• Clemens Hammacher's avatar
    [wasm] Decode local names for debugging · 07752032
    Clemens Hammacher authored
    When providing scope information (containing the value of local
    variables of live stack frames), decode the local variable names of all
    functions in a wasm module and store this in the WasmDebugInfo
    structure.
    Use these names to actually name the reported locals, instead of using
    the default names "param#<d>" and "local#<d>". These names are only used
    as fallbacks for locals which were not assigned a name.
    
    R=titzer@chromium.org,kozyatinskiy@chromium.org
    BUG=v8:6245
    
    Change-Id: Ibf7d30e392248ef5590177cd8b6329239b45e018
    Reviewed-on: https://chromium-review.googlesource.com/548495
    Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
    Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#46379}
    07752032
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer 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...
preparser Loading commit data...
promises-aplus Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn 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...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...