aa101ca18f
This CL removes the bailout when trying to collect the scope info for the class member initializer function. While this might not have worked previously, now we only need to tweak the scope search slightly to fix this. Class member initializer functions never have their own context but instead us the class context. That means that most of the logic in debug-scopes.cc doesn't really matter and we only need to initialize the ScopeIterator properly with the class context and the member initializer JSFunction. Note that this still does not fully fix bug 1350842. That is because we still run into a DCHECk when paused at a `new class { ... }` statement. We'll fix that in a separate CL. R=bmeurer@chromium.org Bug: chromium:1350842 Change-Id: Id128b10676a5aa8a77309735e755e485f2c14446 Fixed: chromium:1246889 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3825881 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/main@{#82387} |
||
---|---|---|
.. | ||
console | ||
cpu-profiler | ||
debugger | ||
heap-profiler | ||
regress | ||
runtime | ||
sessions | ||
type-profiler | ||
BUILD.gn | ||
DEPS | ||
DIR_METADATA | ||
frontend-channel.h | ||
inspector-test.cc | ||
inspector.status | ||
isolate-data.cc | ||
isolate-data.h | ||
json-parse-expected.txt | ||
json-parse.js | ||
OWNERS | ||
print-method-not-found-expected.txt | ||
print-method-not-found.js | ||
protocol-test.js | ||
task-runner.cc | ||
task-runner.h | ||
tasks.cc | ||
tasks.h | ||
testcfg.py | ||
utils.cc | ||
utils.h | ||
wasm-inspector-test.js |