d180d40d28
The DevTools frontend doesn't want the Wasm module's understanding of function body offsets (i.e. including locals), but the ranges of offsets where breakpoints can be set (i.e. only where instructions are). This patch adjusts the reported offsets accordingly. A consequence is that we have to report full (start,end) pairs for each function, instead of being able to dedupe end1==start2 etc. Bug: v8:12917 Change-Id: I0c7d2d96435cdac2c4553647b7bcc8783bc1798b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3780526 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> Cr-Commit-Position: refs/heads/main@{#81887}
34 lines
1.1 KiB
Plaintext
34 lines
1.1 KiB
Plaintext
Tests disassembling wasm scripts
|
|
Session #1: Script parsed. URL: wasm://wasm/moduleName-70e7540a.
|
|
Session #1: Source for wasm://wasm/moduleName-70e7540a:
|
|
bytecode:
|
|
0x00 0x61 0x73 0x6d 0x01 0x00 0x00 0x00 ;; offset 0..7
|
|
0x01 0x09 0x02 0x60 0x01 0x6f 0x01 0x7f ;; offset 8..15
|
|
0x60 0x00 0x00 0x03 0x03 0x02 0x00 0x01 ;; offset 16..23
|
|
0x0a 0x12 0x02 0x0b 0x02 0x01 0x7f 0x01 ;; offset 24..31
|
|
0x7c 0x20 0x01 0x1a 0x41 0x2a 0x0b 0x04 ;; offset 32..39
|
|
0x00 0x01 0x01 0x0b 0x00 0x27 0x04 0x6e ;; offset 40..47
|
|
0x61 0x6d 0x65 0x00 0x0b 0x0a 0x6d 0x6f ;; offset 48..55
|
|
0x64 0x75 0x6c 0x65 0x4e 0x61 0x6d 0x65 ;; offset 56..63
|
|
0x01 0x09 0x02 0x00 0x02 0x66 0x31 0x01 ;; offset 64..71
|
|
0x02 0x66 0x32 0x02 0x08 0x01 0x00 0x01 ;; offset 72..79
|
|
0x01 0x03 0x78 0x79 0x7a
|
|
streamid: undefined
|
|
functionBodyOffsets: 33,39,41,44
|
|
totalNumberOfLines: 13
|
|
lines:
|
|
(module $moduleName
|
|
(func $f1 (;0;) (param $var0 externref) (result i32)
|
|
(local $xyz i32)
|
|
(local $var2 f64)
|
|
local.get $xyz
|
|
drop
|
|
i32.const 42
|
|
)
|
|
(func $f2 (;1;)
|
|
nop
|
|
nop
|
|
)
|
|
)
|
|
bytecodeOffsets: 0,28,28,28,33,35,36,38,40,41,42,43,85
|