• Clemens Hammacher's avatar
    [wasm] Allow for arbitrarily long error messages · 072d0e3e
    Clemens Hammacher authored
    We currently have a fixed limit of 256 characters for error messages
    generated in the decoder. However, we sometimes embed names in it,
    which makes it easy to generate a crash by using long names (e.g. for
    exports) in invalid wasm modules.
    This CL fixes this by switching to a stream based interface, allowing
    to pass arbitrary objects to be printed. With this interface, we can
    easily limit the length of output later.
    
    R=titzer@chromium.org
    
    Bug: chromium:740023
    Change-Id: I2848c31c63a015157e2a3a9458b54e523060cd69
    Reviewed-on: https://chromium-review.googlesource.com/565282Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
    Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#46860}
    072d0e3e
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...