AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
0ff8205261
v8/test/inspector/runtime/client-console-api-message-expected.txt

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

9 lines
285 B
Plaintext
Raw Normal View History

[inspector] avoid cloning of async call chains - separated V8StackTraceImpl and AsyncStackTrace, - V8Debugger owns all AsyncStackTrace and cleanup half of them when limit is reached (first created - first cleaned), - V8StackTraceImpl, AsyncStackTrace and async-task-related tables in V8Debugger have weak reference to other async stack traces. - async tasks are cleared with related async stacks. BUG=v8:6189 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2816043006 Cr-Original-Commit-Position: refs/heads/master@{#44670} Committed: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
Checks that we passed correct arguments in V8InspectorClient::consoleAPIMessage. Note: lines and columns are 1-based.
inspector: report kMessageLog as a level for console.log to embedder Some embedders might want to process console.info and console.log differently. So inspector needs to return a different level for these console log messages. Change-Id: I936990a25f079a0d72f877a5095ed93819fc539a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3331929 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Alexey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/main@{#78357}
2021-12-11 04:52:58 +00:00
log: 42 (:1:9)
[inspector] avoid cloning of async call chains - separated V8StackTraceImpl and AsyncStackTrace, - V8Debugger owns all AsyncStackTrace and cleanup half of them when limit is reached (first created - first cleaned), - V8StackTraceImpl, AsyncStackTrace and async-task-related tables in V8Debugger have weak reference to other async stack traces. - async tasks are cleared with related async stacks. BUG=v8:6189 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2816043006 Cr-Original-Commit-Position: refs/heads/master@{#44670} Committed: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
at (anonymous function) (:1:9)
inspector: report kMessageLog as a level for console.log to embedder Some embedders might want to process console.info and console.log differently. So inspector needs to return a different level for these console log messages. Change-Id: I936990a25f079a0d72f877a5095ed93819fc539a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3331929 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Alexey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/main@{#78357}
2021-12-11 04:52:58 +00:00
info: 239 (:13:15)
[inspector] avoid cloning of async call chains - separated V8StackTraceImpl and AsyncStackTrace, - V8Debugger owns all AsyncStackTrace and cleanup half of them when limit is reached (first created - first cleaned), - V8StackTraceImpl, AsyncStackTrace and async-task-related tables in V8Debugger have weak reference to other async stack traces. - async tasks are cleared with related async stacks. BUG=v8:6189 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2816043006 Cr-Original-Commit-Position: refs/heads/master@{#44670} Committed: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
at b (:13:15)
at a (:15:5)
at consoleTrace (:17:3)
at (anonymous function) (:1:1)
Reference in New Issue Copy Permalink