eb36a7dbcf
If the imported wasm function is being debugged (i.e. redirects to the interpreter), call it via the JS_TO_WASM stub, such that we can disable the breakpoint later by patching the exported function. This also contains a drive-by fix in wasm-translation.cc (for the case that all known positions are bigger than the requested one). R=titzer@chromium.org, kozyatinskiy@chromium.org BUG=v8:5971, v8:5822 Review-Url: https://codereview.chromium.org/2720813002 Cr-Commit-Position: refs/heads/master@{#43583}
24 lines
482 B
Plaintext
24 lines
482 B
Plaintext
Installing code and global variable.
|
|
Calling instantiate function for module A.
|
|
Waiting for wasm script to be parsed.
|
|
Got wasm script!
|
|
Setting breakpoint in line 1:
|
|
func $func
|
|
#nop
|
|
end
|
|
|
|
Calling instantiate function for module B.
|
|
Calling main function on module B.
|
|
Paused at 1:2.
|
|
func $func
|
|
#nop
|
|
end
|
|
|
|
Getting current stack trace via "new Error().stack".
|
|
Error
|
|
at v8://test/getStack:1:1
|
|
at main (<WASM>[1]+1)
|
|
at v8://test/runWasm:1:22
|
|
exports.main returned.
|
|
Finished.
|