AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
b4f1e24078
v8/test/inspector/debugger/framework-nested-scheduled-break-expected.txt

42 lines
939 B
Plaintext
Raw Normal View History

[inspector] support for nested scheduled breaks In current implementation we don't support nested scheduled break at all. If one break was scheduled inside another and second one doesn't produce actual break (execution was in blackboxed code or no JavaScript was executed) then second one will clear first scheduled break even if any not blackboxed JavaScript will be executed later. Ambiguous break reason is added for the case when we have more then one scheduled reason. "auxData" in this case contains object with array of { reason: reason, auxData: auxData } objects for each reason in 'reasons' property. BUG=chromium:632405 Review-Url: https://codereview.chromium.org/2678313002 Cr-Commit-Position: refs/heads/master@{#43021}
2017-02-08 01:42:54 +00:00
Checks nested scheduled break in framework code.
break reason: framework-break
break aux data: {
"data": "data for framework-break"
}
[test/inspector] remove any usage of v8::Extension .. replace all of them with prepared global object template. + bonus: wrap inspector related methods with inspector namespace. BUG=none R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2832723004 Cr-Commit-Position: refs/heads/master@{#44785}
2017-04-21 23:41:07 +00:00
doFrameworkBreak (framework.js:20:12)
doFrameworkWork (framework.js:15:12)
frameworkCall (framework.js:9:12)
testFunction (user.js:27:12)
[inspector] support for nested scheduled breaks In current implementation we don't support nested scheduled break at all. If one break was scheduled inside another and second one doesn't produce actual break (execution was in blackboxed code or no JavaScript was executed) then second one will clear first scheduled break even if any not blackboxed JavaScript will be executed later. Ambiguous break reason is added for the case when we have more then one scheduled reason. "auxData" in this case contains object with array of { reason: reason, auxData: auxData } objects for each reason in 'reasons' property. BUG=chromium:632405 Review-Url: https://codereview.chromium.org/2678313002 Cr-Commit-Position: refs/heads/master@{#43021}
2017-02-08 01:42:54 +00:00
(anonymous) (expr.js:0:0)
break reason: ambiguous
break aux data: {
"reasons": [
{
"reason": "top-scheduled-break"
},
{
"reason": "top-framework-scheduled-break",
"auxData": {
"data": "data for top-framework-scheduled-break"
}
}
]
}
callback (user.js:31:17)
doFrameworkWork (framework.js:16:2)
[test/inspector] remove any usage of v8::Extension .. replace all of them with prepared global object template. + bonus: wrap inspector related methods with inspector namespace. BUG=none R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2832723004 Cr-Commit-Position: refs/heads/master@{#44785}
2017-04-21 23:41:07 +00:00
frameworkCall (framework.js:9:12)
testFunction (user.js:27:12)
[inspector] support for nested scheduled breaks In current implementation we don't support nested scheduled break at all. If one break was scheduled inside another and second one doesn't produce actual break (execution was in blackboxed code or no JavaScript was executed) then second one will clear first scheduled break even if any not blackboxed JavaScript will be executed later. Ambiguous break reason is added for the case when we have more then one scheduled reason. "auxData" in this case contains object with array of { reason: reason, auxData: auxData } objects for each reason in 'reasons' property. BUG=chromium:632405 Review-Url: https://codereview.chromium.org/2678313002 Cr-Commit-Position: refs/heads/master@{#43021}
2017-02-08 01:42:54 +00:00
(anonymous) (expr.js:0:0)
break reason: user-break
break aux data: {
"data": "data for user-break"
}
[test/inspector] remove any usage of v8::Extension .. replace all of them with prepared global object template. + bonus: wrap inspector related methods with inspector namespace. BUG=none R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2832723004 Cr-Commit-Position: refs/heads/master@{#44785}
2017-04-21 23:41:07 +00:00
callback (user.js:32:12)
[inspector] support for nested scheduled breaks In current implementation we don't support nested scheduled break at all. If one break was scheduled inside another and second one doesn't produce actual break (execution was in blackboxed code or no JavaScript was executed) then second one will clear first scheduled break even if any not blackboxed JavaScript will be executed later. Ambiguous break reason is added for the case when we have more then one scheduled reason. "auxData" in this case contains object with array of { reason: reason, auxData: auxData } objects for each reason in 'reasons' property. BUG=chromium:632405 Review-Url: https://codereview.chromium.org/2678313002 Cr-Commit-Position: refs/heads/master@{#43021}
2017-02-08 01:42:54 +00:00
doFrameworkWork (framework.js:16:2)
[test/inspector] remove any usage of v8::Extension .. replace all of them with prepared global object template. + bonus: wrap inspector related methods with inspector namespace. BUG=none R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2832723004 Cr-Commit-Position: refs/heads/master@{#44785}
2017-04-21 23:41:07 +00:00
frameworkCall (framework.js:9:12)
testFunction (user.js:27:12)
[inspector] support for nested scheduled breaks In current implementation we don't support nested scheduled break at all. If one break was scheduled inside another and second one doesn't produce actual break (execution was in blackboxed code or no JavaScript was executed) then second one will clear first scheduled break even if any not blackboxed JavaScript will be executed later. Ambiguous break reason is added for the case when we have more then one scheduled reason. "auxData" in this case contains object with array of { reason: reason, auxData: auxData } objects for each reason in 'reasons' property. BUG=chromium:632405 Review-Url: https://codereview.chromium.org/2678313002 Cr-Commit-Position: refs/heads/master@{#43021}
2017-02-08 01:42:54 +00:00
(anonymous) (expr.js:0:0)
Reference in New Issue Copy Permalink