1a73f73b3b
The format of the name section changed recently. It now contains subsections of different type (currently for function names or local variable names). This CL changes our internal wasm module builders (in JS and C++) to emit this new format, and changes the decoder to understand it. We currently only parse the function name section, and ignore names of local variables. I will later extend this to parse local variable names when needed for debugging. R=ahaas@chromium.org, rossberg@chromium.org BUG=v8:6222 Change-Id: I2627160c25c9209a3f09abe0b88941ec48b24434 Reviewed-on: https://chromium-review.googlesource.com/470247 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Andreas Rossberg <rossberg@chromium.org> Cr-Commit-Position: refs/heads/master@{#44492}
19 lines
485 B
Plaintext
19 lines
485 B
Plaintext
Check that inspector gets two wasm scripts at module creation time.
|
|
Script #0 parsed. URL: v8://test/testFunction
|
|
Script #1 parsed. URL: v8://test/runTestRunction
|
|
Script #2 parsed. URL: wasm://wasm/wasm-7b04570e/wasm-7b04570e-0
|
|
Script #3 parsed. URL: wasm://wasm/wasm-7b04570e/wasm-7b04570e-1
|
|
Source for wasm://wasm/wasm-7b04570e/wasm-7b04570e-0:
|
|
func $nopFunction
|
|
nop
|
|
end
|
|
|
|
Source for wasm://wasm/wasm-7b04570e/wasm-7b04570e-1:
|
|
func $main
|
|
block
|
|
i32.const 2
|
|
drop
|
|
end
|
|
end
|
|
|