v8/test/inspector/debugger/wasm-stepping-out-from-js-expected.txt
Benedikt Meurer 6f448efbef [inspector] Make wasm tests fail rather than time out.
Consistently use InspectorTest.runAsyncTestSuite() in wasm inspector
tests to make tests easier to debug (they'll fail instead of timing
out in case of errors).

Bug: chromium:1162229, chromium:1071432
Change-Id: I7aada196f9e34071aa1bb059bb45f85f75226060
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2609414
Commit-Queue: Yang Guo <yangguo@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#71908}
2021-01-05 07:38:57 +00:00

40 lines
915 B
Plaintext

Tests stepping out from javascript to a wasm caller
Running test: test
Instantiating.
Running exports.main.
>>> First round
Paused at:
function pauseAlternating() {
if (pause) #debugger;
pause = !pause;
Paused at:
Script wasm://wasm/15df010e byte offset 53: Wasm opcode 0x0b (kExprEnd)
Paused at:
instance.exports.main()#
exports.main returned.
After stepping out of the last script, we should stop right at the beginning of the next script.
>>> Second round
Paused at:
#instance.exports.main()
exports.main returned.
The next cycle should work as before (stopping at the "debugger" statement), after stopping at script entry.
>>> Third round
Paused at:
#instance.exports.main()
Paused at:
function pauseAlternating() {
if (pause) #debugger;
pause = !pause;
Paused at:
Script wasm://wasm/15df010e byte offset 53: Wasm opcode 0x0b (kExprEnd)
Paused at:
instance.exports.main()#
exports.main returned.