• jgruber's avatar
    Handle missing context when getting frame details · d2528080
    jgruber authored
    This bug was triggered by a very specific combination:
    
    * A context-allocated variable at script scope.
    * OSR optimization.
    * A scheduled breakpoint, which triggers at stack checks.
    
    Stack checks differ from other possible breakpoint locations in that
    the context (among other things) may be in a register and not on the
    stack, making it impossible to recover during deoptimization. The
    frame_inspector then returns undefined when asked for the context.
    
    In GetFrameDetails, handle this case by omitting all context-allocated
    variables.
    
    BUG=v8:5279
    
    Review-Url: https://codereview.chromium.org/2245603002
    Cr-Commit-Position: refs/heads/master@{#38611}
    d2528080
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
fuzzer Loading commit data...
inspector_protocol_parser_test Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...