Changes to the V8 debugger support which otherwise caused problems with Chrom...

Changes to the V8 debugger support which otherwise caused problems with Chrome.

Added quoting of the name of the ref property using {"ref":1} instead of {ref:1}. The Chrome C++ JSON parser implementation requires quoted property names.

Changed the JSON format for non finite numbers. The previous formatting using NaN, Infinite and -Infinite caused the Chrome C++ JSON parser implementation to fail. Values "NaN", "Infinite" and "-Infinite" (incuding quotes) are now used.

Reverted changes to DebugLookupResultValue (runtime.cc) from http://codereview.chromium.org/17377. The change caused callback into Chrome with the current V8 context expected to have a DOM Window global object. This is not the case when the debugger context is the active context. This causes properties from interceptors and accessors to be reported as undefined in the debugger.

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

[Christian Plesner Hansen, 2009-01-19 15:17:54]

Lgtm, though using strings for numbers doesn't smell good.

[Søren Thygesen Gjesse, 2009-01-19 15:20:35]

On 2009/01/19 15:17:54, Christian Plesner Hansen wrote:
> Lgtm, though using strings for numbers doesn't smell good.

Thats right, but in the debugger protocol the value always have a type:

{"type"="number", "value"="NaN"} (or {"type"="number", "value"=42} for a finite
number).