Bug 6848 - Index out of range exception with New builder
Summary: Index out of range exception with New builder
Status: CLOSED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-12 10:27 EST by John Arthorne CLA
Modified: 2003-03-17 10:55 EST (History)
0 users

See Also:

Attachments
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 John Arthorne CLA 2001-12-12 10:27:36 EST 
This was reported on the newsgroup.  The report is by "ni bin" on Dec 11, 
8:14PM.  He or she only gives a stack trace, no more information.  This is in 
build 2001-12-06.  Here is the stack:

java.lang.StringIndexOutOfBoundsException: String index out of range: -19
 at java.lang.String.substring(String.java:1503)
 at java.lang.String.substring(String.java:1470)
 at
org.eclipse.jdt.internal.core.newbuilder.BuildNotifier.aboutToCompile(BuildN
otifier.java:54)
 at
org.eclipse.jdt.internal.core.newbuilder.AbstractImageBuilder.compile(Abstra
ctImageBuilder.java:185)
 at
org.eclipse.jdt.internal.core.newbuilder.AbstractImageBuilder.compile(Abstra
ctImageBuilder.java:148)
 at
org.eclipse.jdt.internal.core.newbuilder.BatchImageBuilder.build(BatchImageB
uilder.java:47)
 at
org.eclipse.jdt.internal.core.newbuilder.JavaBuilder.buildAll(JavaBuilder.ja
va:103)
 at
org.eclipse.jdt.internal.core.newbuilder.JavaBuilder.build(JavaBuilder.java:
61)
 at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:356)
 at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java
:818)
 at org.eclipse.core.runtime.Platform.run(Platform.java:395)
Comment 1 Kent Johnson CLA 2001-12-12 13:00:42 EST 
This problem was fixed last week and released in the Dec. 11th drop.
Comment 2 Philipe Mulet CLA 2001-12-12 13:17:06 EST 
Bug is actually closed, not fixed (fix was made earlier in 20011211).