Could you please add more tests that exercise different combinations of stackallocated and context allocated variables?
For example, the following script outputs
0: {"visible2":20}
1: {"visible1":10}
because all other variables are stack allocated. Would Dev-tools work
correctly
in such cases?
I think it's quite ok in this case. I expect that function scopes will be consistent with scopes that are visible on stack when you debug inside this function. For example "invisible1" won't be visible in both cases. My main intent here is that there is very well defined static data, that isvisible to programmer only in certain circumstances (when function is on stack). This same data display should be available to user in debugger at any moment.
https://chromiumcodereview.appspot.com/10171003/ -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
