Community
Participate
Working Groups
Build Identifier: 20100917-0705 When trying to visualize the type hierarchy of the interface java.util.SortedSet<E> (or even java.util.NavigableSet<E>) in the "Type Hierarchy" view, a StackOverflowError occurs and I'm requested to exit the workbench. Reproducible: Always Steps to Reproduce: 1. Open "Type Hierarchy" view 2. Right-click, "Focus On..." 3. Select java.util.SortedSet<E> or java.util.NavigableSet<E>
Created attachment 197983 [details] Stacktrace of the error
Tried again in build 20110301-1815. Worked for java.util.SortedSet<E>, but not for java.util.NavigableSet<E>.
Created attachment 197985 [details] Stacktrace of the error in newer version
Satyam, please investigate.
I am unable to reproduce. Which version of JRE classes are you looking at? This error could have been possible only if there is a cycle in the hierarchy.
(In reply to comment #5) > I am unable to reproduce. Which version of JRE classes are you looking at? This > error could have been possible only if there is a cycle in the hierarchy. Hi. I'm looking at the sources of the JRockit VM (build 1.6.0_05-b13). However, I could reproduce it in the Sun JVM sources, installed through apt-get in Ubuntu 10.04 (build 1.6.0_24-b07).
(In reply to comment #6) > Hi. I'm looking at the sources of the JRockit VM (build 1.6.0_05-b13). However, > I could reproduce it in the Sun JVM sources, installed through apt-get in > Ubuntu 10.04 (build 1.6.0_24-b07). It is likely to run into this problem if there is a cycle even in the subtypes of NavigableSet in any dependent jar. Could you try to reproduce in any fresh workspace? I will try to get some fix to avoid these cases, but there is definitely something wrong in your dependent jar files, which you may want to get rid of.
(In reply to comment #7) > (In reply to comment #6) > > Hi. I'm looking at the sources of the JRockit VM (build 1.6.0_05-b13). However, > > I could reproduce it in the Sun JVM sources, installed through apt-get in > > Ubuntu 10.04 (build 1.6.0_24-b07). > It is likely to run into this problem if there is a cycle even in the subtypes > of NavigableSet in any dependent jar. Could you try to reproduce in any fresh > workspace? I will try to get some fix to avoid these cases, but there is > definitely something wrong in your dependent jar files, which you may want to > get rid of. Yes, you were right. I could not reproduce it in a fresh workspace. I'll take a look at my build path, thanks.
Satyam, should this be closed as WORKSFORME ?
I think we could add some checks to report a problem rather than throwing an exception.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
