Summary: | NPE during computePriority for problems | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philippe Krief <pjkrief> | ||||||
Component: | Core | Assignee: | Maxime Daniel <maxime_daniel> | ||||||
Status: | VERIFIED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | daniel_megert, morten-eclipse | ||||||
Version: | 3.1 | ||||||||
Target Milestone: | 3.1.1 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows 2000 | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Philippe Krief
2005-06-21 12:04:40 EDT
I get also the same kind of stack trace with the following header message: Error in JDT Core during AST creation Managed to isolate some of the needed conditions for this to happen (especially, error in binary file that gets reported - triggers a null context for the error, need to have more errors than the max errors nb per compilation unit, need to avoid having regular errors). Haven't got a reliable test case yet though. (Philippe, any more details will be welcome!) I believe that the attached patch removes the problem (from an analysis of the code). This has not undergone full testing yet and should be considered as work in progress. Created attachment 23826 [details]
Tentative patch - not fully tested yet
The rationale of the patch is to synchronize the lifecycles of two attributes
that are allocated under the same conditions, thus should be accessed under the
same conditions as well.
Good candidate for 3.1.1 Checked fix proposed in comment #3 against Build id: I20050624-0010 without problem. Still no reliable test case. Maxime, I can't provide more input. Sorry about that Philippe No problem. I believe we have a serious hint about the solution. Thx for your help. Checked the suggested patch against 3.1 maintenance. Update title to reflect the issue. Created attachment 26912 [details]
Updated patch
Fixed and released in 3.1 maintenance stream. We could not get a reproducable test case, but we now managed firstErrors and problemsMap in a consistent way. Fixed and released in HEAD. Verified using I20050920-0010 for 3.2M2 Verified using M20050923-1430 for 3.1.1 *** Bug 112003 has been marked as a duplicate of this bug. *** |