Include basic scopes information in 'backtrace' response

Sending scope types and object refs costs nothing but would save us request that should be send to retrieve scopes informations for each frame in 'backtrace' response.

Committed: http://code.google.com/p/v8/source/detail?r=2237

[Søren Thygesen Gjesse, 2009-06-22 06:42:28]

LGTM

http://codereview.chromium.org/131107/diff/1/2
File src/mirror-delay.js (right):

http://codereview.chromium.org/131107/diff/1/2#newcode2240
Line 2240: type: scope.scopeType(),
I think you ahould add
  index: i,
even though it will be equal to the array index.

http://codereview.chromium.org/131107/diff/1/2#newcode2241
Line 2241: ref: scope.scopeObject().handle()
For transient scope objects (negative handles) you should skip the ref to the
handle, as it cannot be retrieved through that id anyway.

[yurys, 2009-06-22 07:21:56]

http://codereview.chromium.org/131107/diff/1/2
File src/mirror-delay.js (right):

http://codereview.chromium.org/131107/diff/1/2#newcode2240
Line 2240: type: scope.scopeType(),
On 2009/06/22 06:42:28, Søren Gjesse wrote:
> I think you ahould add
>   index: i,
> even though it will be equal to the array index.

Done.

http://codereview.chromium.org/131107/diff/1/2#newcode2241
Line 2241: ref: scope.scopeObject().handle()
On 2009/06/22 06:42:28, Søren Gjesse wrote:
> For transient scope objects (negative handles) you should skip the ref to the
> handle, as it cannot be retrieved through that id anyway.

Done.

[yurys, 2009-06-22 08:45:19]

http://codereview.chromium.org/131107/diff/1/2
File src/mirror-delay.js (right):

http://codereview.chromium.org/131107/diff/1/2#newcode2241
Line 2241: ref: scope.scopeObject().handle()
On 2009/06/22 06:42:28, Søren Gjesse wrote:
> For transient scope objects (negative handles) you should skip the ref to the
> handle, as it cannot be retrieved through that id anyway.
What do you mean by 'it cannot be retrieved through that id', the scope object
mirror is put into the mirror cache in MakeMirror?