Summary: | Member.getJavadocRange() causes AIOOBE | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> | ||||||
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||||
Status: | VERIFIED FIXED | QA Contact: | |||||||
Severity: | major | ||||||||
Priority: | P3 | ||||||||
Version: | 3.2 | ||||||||
Target Milestone: | 3.2 M4 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Dani Megert
2005-12-14 11:45:52 EST
I never succeeded to get this AIOOBE strictly following your scenario... I tried with a small example as suggested and also with our biggest CU (Parser.java) to have long time for reconciling. I even launched a full build of my workspace to slow my box but never got it... Are you able to reproduce easily? How fast should I need to be between step 3 and 4? I guess this is with 3.2... The member needs to check if the compilation is consistent before returning the javadoc range. I am working on a fix. Would null be acceptable in this case? Created attachment 31757 [details]
Proposed fix
Dani, could you please give it a try?
Created attachment 31758 [details]
Regression test
Fixed and released in HEAD. Regression test added in org.eclipse.jdt.core.tests.model.CompilationUnitTests.test120902 Applied patch on HEAD of JDT Core and it works for me. Thanks. Verified with I20051214-1600 for 3.2M4 |