v8/test/inspector/debugger/restart-frame/restart-top-frame-local-variables-expected.txt
Simon Zünd 8278cb5015 [inspector] Re-enable Debugger#restartFrame
Doc: https://bit.ly/revive-restart-frame

This CL "undeprecates" Debugger#restartFrame and adds a new optional
"mode" parameter for back-wards compatibility. Moreover, the return
values are all deprecated. They were never actually used in the
DevTools frontend and the same information is available from the
Debugger#paused event that fires once execution stops at the
beginning of the restarted function.

The CL also re-baselines all the restart-frame inspector tests that
now run successfully.

R=bmeurer@chromium.org, kimanh@chromium.org

Bug: chromium:1303521
Change-Id: I34bddeb1f2f4ff3dee58dd82e779c111495566f3
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3616505
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Kim-Anh Tran <kimanh@chromium.org>
Commit-Queue: Simon Zünd <szuend@chromium.org>
Cr-Commit-Position: refs/heads/main@{#80491}
2022-05-12 14:24:58 +00:00

73 lines
1.1 KiB
Plaintext

Checks that after restarting the top frame, local variables are reset
Paused at (after evaluation):
let z = 'some let';
#debugger;
}
Pause stack:
foo:5 (canBeRestarted = true)
Evaluating x:
{
id : <messageId>
result : {
result : {
type : string
value : some var
}
}
}
Evaluating y:
{
id : <messageId>
result : {
result : {
type : string
value : some const
}
}
}
Evaluating z:
{
id : <messageId>
result : {
result : {
type : string
value : some let
}
}
}
Restarting function "foo" ...
Paused at (after restart):
function foo() {
var x = #'some var';
const y = 'some const';
Evaluating x:
{
id : <messageId>
result : {
result : {
type : undefined
}
}
}
Evaluating y:
{
id : <messageId>
result : {
result : {
type : undefined
}
}
}
Evaluating z:
{
id : <messageId>
result : {
result : {
type : undefined
}
}
}