From the mail thread:

Scopes in the inspector protocol seem to be missing the 'eval' scope type (Debug.ScopeType.Eval). We'd need these for a couple of our internal tests (e.g. debug-eval-scope.js), and they should probably also show up in DevTools. Do you have any plans to add eval scopes to the protocol? To DevTools? If you like, I can look into adding it to the protocol in the next couple of days.

Secondly, we recently added support for accessing the scopes of suspended generator objects in 4cff8218. So far, we cannot use this through inspector, since inspector only sends Scopes on the Debugger.paused event (and any generator on the callstack is not suspended). Do you have any ideas about adding access to suspended generator's scopes to inspector (and DevTools)? Is this something that could be added in the short-term?


Apparently eval scopes exist for strict mode:

d8> eval("'use strict'; var x = 42;")
"use strict"
d8> x
(d8):1: ReferenceError: x is not defined


See also http://stackoverflow.com/questions/9781285/specify-scope-for-eval-in-javascript.

We have a couple of examples in our tests:

test/mjsunit/debug-eval-scope.js:  assertEquals([ debug.ScopeType.Eval,
test/mjsunit/es6/debug-scope-default-param-with-eval.js:      assertEquals([ debug.ScopeType.Eval,
test/mjsunit/regress/regress-5207.js:    assertEquals(debug.ScopeType.Eval, scopes[0].scopeType());