Community
Participate
Working Groups
I20050527-0010 Unfortunately I cannot give more concrete steps to reproduce. Just saw this in the log: java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.parser.SourceTypeConverter.parseMemberValue (SourceTypeConverter.java:811) at org.eclipse.jdt.internal.compiler.parser.SourceTypeConverter.convertAnnotations (SourceTypeConverter.java:563) at org.eclipse.jdt.internal.compiler.parser.SourceTypeConverter.convert (SourceTypeConverter.java:435) at org.eclipse.jdt.internal.compiler.parser.SourceTypeConverter.convert (SourceTypeConverter.java:165) at org.eclipse.jdt.internal.compiler.parser.SourceTypeConverter.buildCompilationUn it(SourceTypeConverter.java:10 8) at org.eclipse.jdt.internal.core.hierarchy.HierarchyResolver.resolve (HierarchyResolver.java:565) at org.eclipse.jdt.internal.core.hierarchy.HierarchyResolver.resolve (HierarchyResolver.java:486) at org.eclipse.jdt.internal.core.hierarchy.HierarchyBuilder.buildSupertypes (HierarchyBuilder.java:119) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.build (IndexBasedHierarchyBuilder.java:136) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.compute (TypeHierarchy.java:320) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.refresh (TypeHierarchy.java:1255) at org.eclipse.jdt.internal.core.CreateTypeHierarchyOperation.executeOperation (CreateTypeHierarchyOperation.java :90) at org.eclipse.jdt.internal.core.JavaModelOperation.run (JavaModelOperation.java:718) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation (JavaModelOperation.java:777) at org.eclipse.jdt.internal.core.SourceType.newSupertypeHierarchy (SourceType.java:671) at org.eclipse.jdt.internal.core.SourceType.newSupertypeHierarchy (SourceType.java:623) at org.eclipse.jdt.internal.corext.util.SuperTypeHierarchyCache.getTypeHierarchy (SuperTypeHierarchyCache.java:88 ) at org.eclipse.jdt.internal.corext.util.SuperTypeHierarchyCache.getTypeHierarchy (SuperTypeHierarchyCache.java:78 ) at org.eclipse.jdt.ui.OverrideIndicatorLabelDecorator.getOverrideIndicators (OverrideIndicatorLabelDecorator.java :160) at org.eclipse.jdt.ui.OverrideIndicatorLabelDecorator.computeAdornmentFlags (OverrideIndicatorLabelDecorator.java :128) at org.eclipse.jdt.ui.OverrideIndicatorLabelDecorator.decorate (OverrideIndicatorLabelDecorator.java:251) at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate (LightweightDecoratorDefinition.jav a:220) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunna ble.run(LightweightDecoratorMa nager.java:67) at org.eclipse.core.internal.runtime.InternalPlatform.run (InternalPlatform.java:1038) at org.eclipse.core.runtime.Platform.run(Platform.java:775) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate (LightweightDecoratorManager.java:289) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations (LightweightDecoratorManager.jav a:275) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run (DecorationScheduler.java:318) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:67)
The NPE can happen only if the field 'parser' is null. Howver it is set to a non-null value 2 lines above, and no other code would set it to null. Suspecting a VM problem. What VM are you runinng Eclipse on ?
I was running in an old test workspace with an old vm: java.fullversion=J2RE 1.4.2 IBM J9 2.2 Windows XP x86-32 j9n142-20040831 (JIT enabled) J9VM - 20040827_2136_lHdSMR JIT - r7_level20040827_1801 If the other candidates (memberValue and this.unit) are guaranteed to be non- null, close the bug
'memberValue' and 'this.unit' could not cause a NPE on this line. Closing as VM bug.
It happened again in 3.2 RC4 (see bug 142506). After a second look at the code, the NPE can happen if 'memberValue' is null since we're getting its length. Reopening
*** Bug 150520 has been marked as a duplicate of this bug. ***
This looks like the same bug as this https://bugs.eclipse.org/bugs/show_bug.cgi?id=168088 the line numbers changed but the call chain is the same
Thanks Scott. This indeed looks like a dup. *** This bug has been marked as a duplicate of bug 168088 ***