Object keys should always be String, but debugger inconsistently parses them as Int

[GoogleCodeExporter]

Chromium JavaScript Remote Debugger Version: 0.3.6.201207022103
Eclipse version: 3.7.2 Build id: I20110613-1736
OS + version: Ubuntu 12.04.1 LTS

What steps will reproduce the problem?
1. Create an object with two keys like so:
var test = { 
    "1000000000" : {}, 
    "8302611133" : {} 
};

2. Run script and stop the debugger after test is assigned. Inspect test in 
Variables Explorer

What is the expected result?
Both keys should be parsed as string

What happens instead?
Key "1000000000" is parsed as Integer and "8302611133" is parsed as String.

Please provide any additional information below. If possible, attach a
(reduced) test-case.

With some keys, both are parsed as Integer and the Variables Explorer window 
will crash.  For example with "1000000000" and "3302611133. I think the 
debugger inadvertedly parses these as array keys and fills up the memory with 
undefined keys between the first and the second number.

More detailed description in my bugreport at Eclipse:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=388346

Or Stack Overflow, although I didn't fully realize what happened back then:
http://stackoverflow.com/questions/12159854/v8-debugger-in-eclipse-logic-or-weir
dest-bug-ever

Attached file is ~/workspace/.metadata/.log. Steps I took to create this log:
1) remove old .log
2) start Eclipse with a project that demonstrates the bug
3) add a breakpoint to a file called debugtest.js
4) run node.js in break-mode with debugtest.js
5) inspect variable called debugMe, designed to break the Variables Explorer
6) stop and exit.

Original issue reported on code.google.com by redsandro on 10 Sep 2012 at 11:14

• Merged into: #76

Attachments:

• org.chromium.debug.core.log

[GoogleCodeExporter]

V8 Embedder: Node.JS

Original comment by peter.ry...@gmail.com on 11 Sep 2012 at 12:04

• Changed state: Accepted

[GoogleCodeExporter]

Split into two issues: 
http://code.google.com/p/chromedevtools/issues/detail?id=76 and 
http://code.google.com/p/chromedevtools/issues/detail?id=77
and is replaced by them.

Original comment by peter.ry...@gmail.com on 12 Sep 2012 at 4:57

• Changed state: Duplicate