• dslomov's avatar
    Do not assign positions to parser-generated desugarings. · 49c3a606
    dslomov authored
    The root cause for the bug is that the positions assigned to desugared
    code was inconsistent with the source ranges of block scopes.
    Since the fact that the position is assigned causes the debugger to
    break at the parser-generated statement, the fix is to remove positions
    from those nodes that we do not want to break on.
    
    The CL also teaches Hydrogen to tolerate these cases.
    
    R=adamk@chromium.org,rossberg@chromium.org
    BUG=chromium:468661
    LOG=Y
    
    Review URL: https://codereview.chromium.org/1032653002
    
    Cr-Commit-Position: refs/heads/master@{#27424}
    49c3a606
Name
Last commit
Last update
..
regress-2034.js Loading commit data...
regress-2156.js Loading commit data...
regress-2186.js Loading commit data...
regress-2243.js Loading commit data...
regress-2322.js Loading commit data...
regress-2506.js Loading commit data...
regress-2681.js Loading commit data...
regress-2691.js Loading commit data...
regress-2829.js Loading commit data...
regress-2858.js Loading commit data...
regress-3280.js Loading commit data...
regress-3426.js Loading commit data...
regress-347906.js Loading commit data...
regress-3683.js Loading commit data...
regress-3741.js Loading commit data...
regress-3902.js Loading commit data...
regress-3938.js Loading commit data...
regress-411237.js Loading commit data...
regress-468661.js Loading commit data...
regress-cr372788.js Loading commit data...
regress-crbug-248025.js Loading commit data...
regress-crbug-346141.js Loading commit data...