Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(4)

Issue 2721633004: [inspector] fixed crash on attempt to access empty scope_info on break (Closed)

Created:
3 years, 9 months ago by kozy
Modified:
3 years, 9 months ago
Reviewers:
Yang, Toon Verwaest
CC:
v8-reviews_googlegroups.com, devtools-reviews_chromium.org
Target Ref:
refs/pending/heads/master
Project:
v8
Visibility:
Public.

Description

[inspector] fixed crash on attempt to access empty scope_info on break Nested arrow functions could have empty scope_info, we need to ensure its creation. BUG=chromium:696202 R=yangguo@chromium.org

Patch Set 1 #

Patch Set 2 : better test #

Unified diffs Side-by-side diffs Delta from patch set Stats (+48 lines, -2 lines) Patch
M src/ast/scopes.cc View 1 chunk +4 lines, -2 lines 0 comments Download
A test/inspector/debugger/step-into-arrow.js View 1 1 chunk +20 lines, -0 lines 0 comments Download
A test/inspector/debugger/step-into-arrow-expected.txt View 1 1 chunk +23 lines, -0 lines 0 comments Download
M test/inspector/protocol-test.js View 1 1 chunk +1 line, -0 lines 0 comments Download

Messages

Total messages: 6 (2 generated)
kozy
Yang, please take a look! I think that root of issue is skipping scope without ...
3 years, 9 months ago (2017-02-27 22:29:05 UTC) #2
Yang
LGTM. Toon, could you give this a look?
3 years, 9 months ago (2017-02-28 12:43:13 UTC) #4
Toon Verwaest
This doesn't seem like the correct fix to me. Scope info allocation for the debugger ...
3 years, 9 months ago (2017-02-28 14:19:58 UTC) #5
Yang
3 years, 9 months ago (2017-03-14 12:16:43 UTC) #6
On 2017/02/28 14:19:58, Toon Verwaest wrote:
> This doesn't seem like the correct fix to me. Scope info allocation for the
> debugger should only happen for a single function at a time. There's probably
> something going wrong with scope info allocation of the arrow function when we
> step into it? 
> 
> I think the current fix will still fail if the arrow function we step into is
a
> sibling rather than nested?

The correct fix is here: https://codereview.chromium.org/2751573003#

Powered by Google App Engine
This is Rietveld 408576698