v8/test/inspector/debugger/get-possible-breakpoints-array-literal-expected.txt

Tests possible breakpoints in array literal
{
    id : <messageId>
    result : {
        locations : [
            [0] : {
                columnNumber : 0
                lineNumber : 0
                scriptId : <scriptId>
            }
            [1] : {
                columnNumber : 6
                lineNumber : 0
                scriptId : <scriptId>
            }
            [2] : {
                columnNumber : 7
                lineNumber : 0
                scriptId : <scriptId>
                type : return
            }
            [3] : {
                columnNumber : 8
                lineNumber : 0
                scriptId : <scriptId>
                type : return
            }
        ]
    }
}
[inspector] Refactor protocol-test.js This refactoring makes it easier to write advanced tests and gives full control over what's happening to the test code. It also forces description for every test. BUG=none Review-Url: https://codereview.chromium.org/2891213002 Cr-Commit-Position: refs/heads/master@{#45412} 2017-05-19 00:35:45 +00:00			`Tests possible breakpoints in array literal`
Compiling an array literal should be context-independent. We are removing use of the debugger context. When the debugger triggers compilation, we may not have a context from which to create a JSArray. R=ishell@chromium.org BUG=chromium:664577 Review-Url: https://codereview.chromium.org/2479123002 Cr-Commit-Position: refs/heads/master@{#40956} 2016-11-14 10:46:06 +00:00			`{`
			`id : <messageId>`
			`result : {`
			`locations : [`
			`[0] : {`
			`columnNumber : 0`
			`lineNumber : 0`
			`scriptId : <scriptId>`
			`}`
			`[1] : {`
			`columnNumber : 6`
			`lineNumber : 0`
			`scriptId : <scriptId>`
			`}`
			`[2] : {`
			`columnNumber : 7`
			`lineNumber : 0`
			`scriptId : <scriptId>`
[inspector] added type of break location into getPossibleBreakpoints output This CL provide type with each break location, type could be: call, return or debugger statement. BUG=chromium:432469 R=yangguo@chromium.org,dgozman@chromium.org Review-Url: https://codereview.chromium.org/2728563002 Cr-Commit-Position: refs/heads/master@{#43619} 2017-03-06 20:47:55 +00:00			`type : return`
Compiling an array literal should be context-independent. We are removing use of the debugger context. When the debugger triggers compilation, we may not have a context from which to create a JSArray. R=ishell@chromium.org BUG=chromium:664577 Review-Url: https://codereview.chromium.org/2479123002 Cr-Commit-Position: refs/heads/master@{#40956} 2016-11-14 10:46:06 +00:00			`}`
			`[3] : {`
			`columnNumber : 8`
			`lineNumber : 0`
			`scriptId : <scriptId>`
[inspector] added type of break location into getPossibleBreakpoints output This CL provide type with each break location, type could be: call, return or debugger statement. BUG=chromium:432469 R=yangguo@chromium.org,dgozman@chromium.org Review-Url: https://codereview.chromium.org/2728563002 Cr-Commit-Position: refs/heads/master@{#43619} 2017-03-06 20:47:55 +00:00			`type : return`
Compiling an array literal should be context-independent. We are removing use of the debugger context. When the debugger triggers compilation, we may not have a context from which to create a JSArray. R=ishell@chromium.org BUG=chromium:664577 Review-Url: https://codereview.chromium.org/2479123002 Cr-Commit-Position: refs/heads/master@{#40956} 2016-11-14 10:46:06 +00:00			`}`
			`]`
			`}`
			`}`