Summary: | Unable to build problem | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Lynne Kues <lynne_kues> | ||||
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | major | ||||||
Priority: | P3 | CC: | n.a.edgar, slavescu, theivend, veronika_irvine | ||||
Version: | 2.1 | ||||||
Target Milestone: | 2.1 RC4 | ||||||
Hardware: | PC | ||||||
OS: | Windows 2000 | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Lynne Kues
2003-03-26 16:30:25 EST
Created attachment 4358 [details]
walkback traces written to dos window
Appears to be related to loading the swt examples project. If I do not load this, I can build successfully. Ignore above statement, even if I don't have the examples project loaded I still cannot build. Lynne, could you please try with another VM? Or try disabling the jit (passing - vmArgs -Djava.compiler=NONE) I suspect this is another case of a jit problem with SR2. Disabling the jit or using a different vm solves the problem. I guess this is expected. I thought it was odd because I have been using the 1.3.1 SR2 vm for awhile, but I ran into this problem starting with Monday's build. Reproduced and isolated source pattern causing grief to SR2 JIT. if replacing following code ... unitScope.recordReference(unitScope.fPackage.compoundName, name); Binding binding = unitScope.fPackage.getTypeOrPackage(name); ... with following using an extra local variable 'currentPackage' ... PackageBinding currentPackage = unitScope.fPackage; unitScope.recordReference(currentPackage.compoundName, name); Binding binding = currentPackage.getTypeOrPackage(name); then it runs ok. This is only a workaround for a JIT bug, but still interesting for users of SR2 ... *** Bug 34962 has been marked as a duplicate of this bug. *** *** Bug 35476 has been marked as a duplicate of this bug. *** *** Bug 31497 has been marked as a duplicate of this bug. *** *** Bug 35298 has been marked as a duplicate of this bug. *** *** Bug 35754 has been marked as a duplicate of this bug. *** Candidating for RC4 integration. +1 +1 Fix released for integration Verified |