| Summary: | Opening a class with a SWT Shell throws StringIndexOutOfBoundsException | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Peter Walker <walkerp> | ||||
| Component: | VE | Assignee: | Jonathan Stinton <jstinton> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P1 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 84398 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Peter Walker
Created attachment 17661 [details]
stack trace
This is actually a defect with JDT IScanner(84398) implementation where reusing a IScanner causes a problem. The IScanner implementation doesnt clean up once it is told to scan a new string. Having the old values causes the problem for the new source. Putting in a temporary fix for cleaning up the internal values. This needs to be removed once 84398 gets resolved. Releasing class DefaultScannerFactory. JDT bug 84398 has been fixed in Eclipse 3.1M4. This problem should go away once VE steps up to Eclipse 3.1. Need to verify and close this defect after the move to 3.1. Using Eclipse 3.1m5a and VE N20050311 this bug has been verified as fixed. Verified in VE 1.1M1 RC1 |