This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 164513 - IndexOutOfBoundsException: toIndex = 10
Summary: IndexOutOfBoundsException: toIndex = 10
Status: CLOSED DUPLICATE of bug 156601
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Entlicher
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-05 16:46 UTC by Egor Ushakov
Modified: 2010-04-29 09:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 147007


Attachments
stacktrace (1.39 KB, text/plain)
2009-05-05 16:46 UTC, Egor Ushakov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Egor Ushakov 2009-05-05 16:46:23 UTC
Build: NetBeans IDE 6.7 Beta (Build 200904242137)
VM: Java HotSpot(TM) Client VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03
OS: Windows Vista, 6.0, x86

User Comments:
ivansidorkin: exception during debugging mobile application

minashokry: debug mobile project

ca: Debugging MIDP application



Stacktrace: 
java.lang.IndexOutOfBoundsException: toIndex = 10
        at java.util.SubList.<init>(SubList.java:602)
        at java.util.RandomAccessSubList.<init>(RandomAccessSubList.java:758)
        at java.util.AbstractList.subList(AbstractList.java:468)
        at com.sun.tools.jdi.ThreadReferenceImpl.privateFrames(ThreadReferenceImpl.java:359)
        at com.sun.tools.jdi.ThreadReferenceImpl.frames(ThreadReferenceImpl.java:308)
        at org.netbeans.modules.debugger.jpda.jdi.ThreadReferenceWrapper.frames(ThreadReferenceWrapper.java:227)
Comment 1 Egor Ushakov 2009-05-05 16:46:28 UTC
Created attachment 81577 [details]
stacktrace
Comment 2 Martin Entlicher 2009-05-06 09:26:50 UTC
This is in fact a duplicate of issue #156601, which was fixed for index 13 only.
Apparently, the "fix" did not help at all, when the retrieval of 13 frames fails, it fails for 12 as well. Even though
the frame count *is* 13!

We have now one case with 10. So it looks like it can occur for any number, but 13 is still the most popular one :-)

This exception does not make any sense, therefore it can not be reasonably fixed. Most probably it is some
race-condition in ThreadReferenceImpl.privateFrames() and the Cache.
Comment 3 Martin Entlicher 2009-05-06 09:33:55 UTC
I've reopened the original issue #156601.

*** This issue has been marked as a duplicate of 156601 ***
Comment 4 Quality Engineering 2010-04-29 09:50:50 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.