v8/test/inspector/debugger/wasm-stepping-liftoff-expected.txt
Clemens Backes 3ea7ecaf67 [wasm][debug] Improve printing of break locations
Using the "logSourceLocation" function from protocol-test.js prints
slightly better location information for wasm, and especially much
better information for JS breakpoints. This helps understanding and
debugging these tests.

R=thibaudm@chromium.org

Bug: v8:10351
Change-Id: I51c7d168d2cb19fb8469b4a2eb372c2b95650fcb
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2120539
Reviewed-by: Thibaud Michaud <thibaudm@chromium.org>
Commit-Queue: Clemens Backes <clemensb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#66863}
2020-03-25 17:19:48 +00:00

73 lines
2.7 KiB
Plaintext

Tests stepping through wasm scripts by byte offsets
Setting up global instance variable.
Got wasm script: wasm://wasm/42af3c82
Setting breakpoint on offset 72 (should be propagated to 73, the offset of the call), url wasm://wasm/42af3c82
{
columnNumber : 73
lineNumber : 0
scriptId : <scriptId>
}
Script wasm://wasm/42af3c82 byte offset 73: Wasm opcode 0x10
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 52: Wasm opcode 0x1
Debugger.stepOver called
Script wasm://wasm/42af3c82 byte offset 53: Wasm opcode 0x1
Debugger.stepOut called
Script wasm://wasm/42af3c82 byte offset 75: Wasm opcode 0xc
Debugger.stepOut called
Script wasm://wasm/42af3c82 byte offset 73: Wasm opcode 0x10
Debugger.stepOver called
Script wasm://wasm/42af3c82 byte offset 75: Wasm opcode 0xc
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 59: Wasm opcode 0x20
Debugger.resume called
Script wasm://wasm/42af3c82 byte offset 73: Wasm opcode 0x10
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 52: Wasm opcode 0x1
Debugger.stepOut called
Script wasm://wasm/42af3c82 byte offset 75: Wasm opcode 0xc
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 59: Wasm opcode 0x20
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 61: Wasm opcode 0x4
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 63: Wasm opcode 0x20
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 65: Wasm opcode 0x41
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 67: Wasm opcode 0x6b
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 68: Wasm opcode 0x21
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 70: Wasm opcode 0x41
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 73: Wasm opcode 0x10
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 52: Wasm opcode 0x1
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 53: Wasm opcode 0x1
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 54: Wasm opcode 0xb
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 75: Wasm opcode 0xc
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 59: Wasm opcode 0x20
Debugger.resume called
instance.exports.main(4)#
Debugger.resume called
exports.main returned!
Test stepping over a recursive call
Setting breakpoint on the recursive call instruction @+93, url wasm://wasm/42af3c82
{
columnNumber : 93
lineNumber : 0
scriptId : <scriptId>
}
Script wasm://wasm/42af3c82 byte offset 93: Wasm opcode 0x10
Removing breakpoint
Debugger.stepOver called
Script wasm://wasm/42af3c82 byte offset 95: Wasm opcode 0x20
Debugger.resume called
Finished!