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 148674 - [65cat] ArrayIndexOutOfBoundsException: 2174
Summary: [65cat] ArrayIndexOutOfBoundsException: 2174
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Lexer (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Miloslav Metelka
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-29 20:16 UTC by goeh
Modified: 2008-10-06 12:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 120423

Attachments
stacktrace (4.28 KB, text/plain)
2008-09-29 20:16 UTC, goeh 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description goeh 2008-09-29 20:16:30 UTC 
Build: NetBeans IDE Dev (Build 200809231435)
VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06
OS: Windows XP, 5.1, x86

User Comments:
goeh: Editing a Grails WebFlow controller.
Double-clicked the word Integer in Integer.valueOf(s) and was about to replace Integer with Long. First I got ArrayIndexOutOfBoundsException then a half second later I got NullPointerException.



Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: 2174
        at org.netbeans.lib.lexer.LAState$LargeState.state(LAState.java:408)
        at org.netbeans.lib.lexer.inc.IncTokenList.state(IncTokenList.java:246)
        at org.netbeans.lib.lexer.inc.IncTokenList.replaceTokens(IncTokenList.java:353)
        at org.netbeans.lib.lexer.inc.TokenListUpdater.updateRegular(TokenListUpdater.java:279)
        at org.netbeans.lib.lexer.inc.TokenHierarchyUpdate$UpdateItem.update(TokenHierarchyUpdate.java:346)
        at org.netbeans.lib.lexer.inc.TokenHierarchyUpdate.processLevelInfos(TokenHierarchyUpdate.java:221)
Comment 1 goeh 2008-09-29 20:16:42 UTC 
Created attachment 70832 [details]
stacktrace
Comment 2 Miloslav Metelka 2008-10-06 11:56:42 UTC 
This should be eliminated by fix of issue 144258.
Comment 3 Miloslav Metelka 2008-10-06 12:01:16 UTC 
Since issue 144258 was integrated almost at the time like your testing build was created I would like to ask you to get
a newer dev build and if you would be able to reproduce the problem there please reopen the issue. Thanks.