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 256763 - [newcodemodel] ArrayIndexOutOfBoundsException at org.clank.java.std.memcpy
Summary: [newcodemodel] ArrayIndexOutOfBoundsException at org.clank.java.std.memcpy
Status: RESOLVED INCOMPLETE
Alias: None
Product: cnd
Classification: Unclassified
Component: Code Model (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: petrk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-24 13:15 UTC by Exceptions Reporter
Modified: 2016-07-15 14:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 221328

Attachments
stacktrace (5.26 KB, text/plain)
2015-11-24 13:15 UTC, Exceptions Reporter 		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 Exceptions Reporter 2015-11-24 13:15:24 UTC 
Build: NetBeans IDE 8.1 (Build 201510222201)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.65-b01, Java(TM) SE Runtime Environment, 1.8.0_65-b17
OS: Linux

User Comments:
GUEST: Trying to refactor a method name in an lager C++ project.




Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException
   at org.clank.java.std.memcpy(std.java:4037)
   at org.clang.basic.IdentifierInfoStringMapEntry.Create(IdentifierInfoStringMapEntry.java:188)
   at org.clang.basic.impl.StringMapIdentifierInfo.GetOrCreateValue(StringMapIdentifierInfo.java:343)
   at org.clang.basic.impl.StringMapIdentifierInfo.GetOrCreateValue(StringMapIdentifierInfo.java:372)
   at org.clang.basic.IdentifierTable.get(IdentifierTable.java:179)
   at org.clang.lex.Preprocessor.getIdentifierInfo(Preprocessor.java:1754)
Comment 1 Exceptions Reporter 2015-11-24 13:15:26 UTC 
Created attachment 157477 [details]
stacktrace
Comment 2 petrk 2016-07-15 14:25:21 UTC 
Closed as incomplete because it is difficult to reproduce the bug without test case on updated clank sources. Moreover, that exception may never occur again because of updated clank.