v8/test/inspector/debugger/wasm-stepping-liftoff-expected.txt
Clemens Backes a1d2e34260 [wasm][debug] Fix printing of wasm opcodes
This is a minor cosmetic fix. Wasm opcodes are bytes, hence they should
always be printed as an even number of hexadecimal digits.
Note that currently we only print a single byte anyway, but in the
future we will want to extend this to correctly parse multi-byte
opcodes. Those will also be printed as an even number of characters
then.

R=thibaudm@chromium.org

Bug: v8:10351
Change-Id: I2423277b470d74c1c72cb619c2a43bb978423bc0
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2122025
Reviewed-by: Thibaud Michaud <thibaudm@chromium.org>
Commit-Queue: Clemens Backes <clemensb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#66883}
2020-03-27 07:05:25 +00:00

70 lines
2.6 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 0x01
Debugger.stepOver called
Script wasm://wasm/42af3c82 byte offset 53: Wasm opcode 0x01
Debugger.stepOut called
Script wasm://wasm/42af3c82 byte offset 75: Wasm opcode 0x0c
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 0x0c
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 0x01
Debugger.stepOut called
Script wasm://wasm/42af3c82 byte offset 75: Wasm opcode 0x0c
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 0x04
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 0x01
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 53: Wasm opcode 0x01
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 54: Wasm opcode 0x0b
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 75: Wasm opcode 0x0c
Debugger.stepInto called
Script wasm://wasm/42af3c82 byte offset 59: Wasm opcode 0x20
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!