6f448efbef
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}
15 lines
599 B
Plaintext
15 lines
599 B
Plaintext
Step into a function that starts with a non-breakable opcode (i.e. block), then step from there. See https://crbug.com/1137710.
|
|
|
|
Running test: test
|
|
Setting up global instance variable.
|
|
Got wasm script: wasm://wasm/4658c40e
|
|
Setting breakpoint on offset 44
|
|
Running main function.
|
|
Script wasm://wasm/4658c40e byte offset 44: Wasm opcode 0x10 (kExprCallFunction)
|
|
Debugger.stepInto called
|
|
Script wasm://wasm/4658c40e byte offset 40: Wasm opcode 0x0b (kExprEnd)
|
|
Debugger.stepInto called
|
|
Script wasm://wasm/4658c40e byte offset 41: Wasm opcode 0x0b (kExprEnd)
|
|
Debugger.resume called
|
|
exports.main returned.
|