v8/test/inspector/debugger/set-blackbox-patterns-expected.txt

Tests blackboxing by patterns
Pattern parser error: Uncaught SyntaxError: Invalid regular expression: /(foo([)/: Unterminated character class
Paused in
(...):1
Paused in
(...):1
Paused in
qwe:3
baz:3
(...):1
Paused in
bar:3
foo:3
qwe:3
baz:3
(...):1
Paused in
qwe:4
baz:3
(...):1
Paused in
qwe:4
baz:3
(...):1
Paused in
(...):1
[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 blackboxing by patterns`
[inspector] added inspector test runner [part 5] - added most part of inspector tests that depends only on JavaScript domains. BUG=chromium:635948 R=dgozman@chromium.org,alph@chromium.org Committed: https://crrev.com/9ddbdab195923fc87fae3587ae06c5c1c5ca6d79 Review-Url: https://codereview.chromium.org/2369753004 Cr-Original-Commit-Position: refs/heads/master@{#39897} Cr-Commit-Position: refs/heads/master@{#39931} 2016-10-02 21:22:49 +00:00			`Pattern parser error: Uncaught SyntaxError: Invalid regular expression: /(foo([)/: Unterminated character class`
			`Paused in`
			`(...):1`
			`Paused in`
			`(...):1`
			`Paused in`
			`qwe:3`
			`baz:3`
			`(...):1`
			`Paused in`
			`bar:3`
			`foo:3`
			`qwe:3`
			`baz:3`
			`(...):1`
			`Paused in`
			`qwe:4`
			`baz:3`
			`(...):1`
			`Paused in`
[inspector] improve return position of explicit return in non-async function Goal of this CL: explicit return from non-async function has position after return expression as return position (will unblock [1]). BytecodeArrayBuilder has SetStatementPosition and SetExpressionPosition methods. If one of these methods is called then next generated bytecode will get passed position. It's general treatment for most cases. Unfortunately it doesn't work for Returns: - debugger requires source positions exactly on kReturn bytecode in stepping implementation, - BytecodeGenerator::BuildReturn and BytecodeGenerator::BuildAsyncReturn generates more then one bytecode and general solution will put return position on first generated bytecode, - it's not easy to split BuildReturn function into two parts to allow something like following in BytecodeGenerator::VisitReturnStatement since generated bytecodes are actually controlled by execution_control(). ..->BuildReturnPrologue(); ..->SetReturnPosition(stmt); ..->Return(); In this CL we pass ReturnStatement through ExecutionControl and use it for position when we emit return bytecode right here. So this CL only will improve return position for returns inside of non-async functions, I'll address async functions later. [1] https://chromium-review.googlesource.com/c/543161/ Change-Id: Iede512c120b00c209990bf50c20e7d23dc0d65db Reviewed-on: https://chromium-review.googlesource.com/560738 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#46687} 2017-07-14 17:50:09 +00:00			`qwe:4`
[inspector] added inspector test runner [part 5] - added most part of inspector tests that depends only on JavaScript domains. BUG=chromium:635948 R=dgozman@chromium.org,alph@chromium.org Committed: https://crrev.com/9ddbdab195923fc87fae3587ae06c5c1c5ca6d79 Review-Url: https://codereview.chromium.org/2369753004 Cr-Original-Commit-Position: refs/heads/master@{#39897} Cr-Commit-Position: refs/heads/master@{#39931} 2016-10-02 21:22:49 +00:00			`baz:3`
			`(...):1`
			`Paused in`
			`(...):1`