788bffd532
When stepping in from JS, the stepping frame ID will not be set. Instead of ensuring to set it properly, we can just skip the check for the frame ID. It was needed before, when we didn't properly reset stepping information. Now, it's redundant anyway. Also, ensure that we don't redirect to the interpreter if the --debug-in-liftoff flag is set. Drive-by: Fix and clang-format some parts of the test (no semantic change). R=thibaudm@chromium.org, szuend@chromium.org Bug: v8:10351 Change-Id: I58a3cd68937006c2d6b755a4465e793abcf8a20c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2124317 Reviewed-by: Simon Zünd <szuend@chromium.org> Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#66904}
33 lines
694 B
Plaintext
33 lines
694 B
Plaintext
Tests stepping from javascript into wasm
|
|
Installing code and global variable.
|
|
Calling instantiate function.
|
|
Waiting for wasm scripts to be parsed.
|
|
Ignoring script with url v8://test/callInstantiate
|
|
Got wasm script: wasm://wasm/7d022e0e
|
|
Setting breakpoint on i32.const
|
|
{
|
|
columnNumber : 37
|
|
lineNumber : 0
|
|
scriptId : <scriptId>
|
|
}
|
|
paused
|
|
function test() {
|
|
#debugger;
|
|
instance.exports.main(1);
|
|
|
|
Debugger.stepInto
|
|
paused
|
|
debugger;
|
|
#instance.exports.main(1);
|
|
}
|
|
|
|
Debugger.stepInto
|
|
paused
|
|
Script wasm://wasm/7d022e0e byte offset 35: Wasm opcode 0x20
|
|
Debugger.resume
|
|
paused
|
|
Script wasm://wasm/7d022e0e byte offset 37: Wasm opcode 0x41
|
|
Debugger.resume
|
|
exports.main returned!
|
|
Finished!
|