Summary: | Eclipse is reporting "Could not retrieve superclass" every few minutes | ||||||
---|---|---|---|---|---|---|---|
Product: | [Tools] Objectteams | Reporter: | Peter Steele <pwsteele> | ||||
Component: | OTJ | Assignee: | Stephan Herrmann <stephan.herrmann> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | daniel_megert, stephan.herrmann | ||||
Version: | 2.0 | ||||||
Target Milestone: | 2.0.1 | ||||||
Hardware: | PC | ||||||
OS: | Windows 7 | ||||||
Whiteboard: | Also released in 2.1 M1 | ||||||
Attachments: |
|
Description
Peter Steele
2011-07-20 11:19:53 EDT
Peter, as Dani correctly noticed, the bug doesn't occur in a plain JDT but you have (part of) the Object Teams Development Tooling installed, which ships a variant of the org.eclipse.jdt.core plug-in. Since you didn't list the OTDT in your list of feature you might have installed it by accident and uninstalling the OTDT should fix the issue for you. To do so please look for the feature called "Object Teams Patch for JDT/Core" After uninstalling you may verify that you are back to the original JDT/Core by looking for this plugin: id: org.eclipse.jdt.core version: 3.7.0.v_B61 OTOH, the OTDT is intended to be fully compatible. For the Object Teams Project it would be valuable if you could give more details how to reproduce (and then fix) the problem. Thanks. I was unaware OTDT was installed. I just recently upgraded to Indigo and it likely got included when I was installing other things. I removed this component and the problem appears to have gone away. As for reproducing it, I don't really have any good information. Prior to removing the OTDO component, the exception would simply occur periodically while I was editing. I didn't see any particular pattern in what I was doing at the time when this error would occur. Created attachment 200691 [details]
test & fix
I found a way to reproduce the log entry, which requires a binary type
binding whose super class is a source type binding.
In this specific case the OT/J compiler missed some necessary setup
before calling into ReferenceBinding.superclass() which can trigger
LookupEnvironment.askForType(..), where things went bad.
Fixed by bracketing three more locations in TypeBinding with
Dependencies.{setup,release}.
Committed for 2.0.1 Verified for 2.0.1 using build 201108160141. |