v8/test/debugger/debug/side-effect
Yang Guo 33be2fb1d2 [debug] use flag to decide whether accessor has side effect.
Instead of a hard-coded list of function addresses, we now use a flag
on the AccessorInfo object to annotate whether the getter can cause any
side effect.

Future changes will extend this to InterceptorInfo, CallHandlerInfo, and
expose this through the API.

R=jgruber@chromium.org, luoe@chromium.org

Bug: v8:7515
Change-Id: Id0fedf03493c3bd81913557a5681f8f63660f6a4
Reviewed-on: https://chromium-review.googlesource.com/945909
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#51756}
2018-03-06 09:25:42 +00:00
..
debug-evaluate-no-side-effect-async.js Reland "[debug] add tests, mark side-effect-free (Typed)Array, WeakMap/Set fns" 2018-02-22 19:45:51 +00:00
debug-evaluate-no-side-effect-builtins-2.js Reland "[debug] add tests, mark side-effect-free (Typed)Array, WeakMap/Set fns" 2018-02-22 19:45:51 +00:00
debug-evaluate-no-side-effect-builtins.js Reland "[debug] add tests, mark side-effect-free (Typed)Array, WeakMap/Set fns" 2018-02-22 19:45:51 +00:00
debug-evaluate-no-side-effect-control.js
debug-evaluate-no-side-effect-iife.js
debug-evaluate-no-side-effect-ops.js
debug-evaluate-no-side-effect.js [debug] use flag to decide whether accessor has side effect. 2018-03-06 09:25:42 +00:00