AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
e69325305b
v8/test/inspector/debugger/wasm-stepping-out-from-js-expected.txt

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
915 B
Plaintext
Raw Normal View History

[wasm][debug] Implement stepping out from JS to wasm This specific case was not implemented or tested before. Implementing it actually simplifies some of the existing logic, since StepOut can now reuse the generic logic in debug.cc for all cases (Wasm->Wasm, Wasm->JS, JS->Wasm). Drive-by: 1) Fix typo ("skip" -> "step"). 2) Move the check for Liftoff code from debug.cc to wasm-debug.cc, where it fits better. 3) Remove a TODO which is done already. R=thibaudm@chromium.org, szuend@chromium.org Bug: chromium:1145176 Change-Id: I415ca1d8bacef5b21bf1dafd9e16417ec2d12c7c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2560719 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#71428}
2020-11-26 13:28:06 +00:00
Tests stepping out from javascript to a wasm caller
[inspector] Make wasm tests fail rather than time out. Consistently use InspectorTest.runAsyncTestSuite() in wasm inspector tests to make tests easier to debug (they'll fail instead of timing out in case of errors). Bug: chromium:1162229, chromium:1071432 Change-Id: I7aada196f9e34071aa1bb059bb45f85f75226060 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2609414 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@{#71908}
2021-01-05 05:51:52 +00:00
Running test: test
[wasm][debug] Implement stepping out from JS to wasm This specific case was not implemented or tested before. Implementing it actually simplifies some of the existing logic, since StepOut can now reuse the generic logic in debug.cc for all cases (Wasm->Wasm, Wasm->JS, JS->Wasm). Drive-by: 1) Fix typo ("skip" -> "step"). 2) Move the check for Liftoff code from debug.cc to wasm-debug.cc, where it fits better. 3) Remove a TODO which is done already. R=thibaudm@chromium.org, szuend@chromium.org Bug: chromium:1145176 Change-Id: I415ca1d8bacef5b21bf1dafd9e16417ec2d12c7c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2560719 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#71428}
2020-11-26 13:28:06 +00:00
Instantiating.
Running exports.main.
>>> First round
Paused at:
function pauseAlternating() {
if (pause) #debugger;
pause = !pause;
Paused at:
Script wasm://wasm/15df010e byte offset 53: Wasm opcode 0x0b (kExprEnd)
Paused at:
instance.exports.main()#
exports.main returned.
After stepping out of the last script, we should stop right at the beginning of the next script.
>>> Second round
Paused at:
#instance.exports.main()
exports.main returned.
The next cycle should work as before (stopping at the "debugger" statement), after stopping at script entry.
>>> Third round
Paused at:
#instance.exports.main()
Paused at:
function pauseAlternating() {
if (pause) #debugger;
pause = !pause;
Paused at:
Script wasm://wasm/15df010e byte offset 53: Wasm opcode 0x0b (kExprEnd)
Paused at:
instance.exports.main()#
exports.main returned.
Reference in New Issue Copy Permalink