f4d408fdc4
JavaScript scopes are reported from inner-most to outer-most, while previously we would report WebAssembly frames from outer-most to inner-most. This is quite confusing for developers, and also doesn't really make sense, so this CL fixes this inconsistency. Bug: chromium:1071432 Change-Id: I6a4742f13b9a0df33e50c6fcd40992873996aaf5 Fixed: chromium:1159309 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2602947 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> 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@{#71875}
13 lines
458 B
Plaintext
13 lines
458 B
Plaintext
Tests pausing a running script and stepping
|
|
Instantiate
|
|
Wait for script
|
|
Got wasm script: wasm://wasm/c84b7cde
|
|
Run
|
|
Expecting to pause at 61
|
|
Paused at offset 61; wasm-expression-stack: []; local: [12]
|
|
Paused at offset 62; wasm-expression-stack: []; local: [12]
|
|
Paused at offset 64; wasm-expression-stack: [12]; local: [12]
|
|
Paused at offset 66; wasm-expression-stack: [12, 1]; local: [12]
|
|
Paused at offset 67; wasm-expression-stack: [13]; local: [12]
|
|
Finished!
|