-
Bug
-
Resolution: Fixed
-
P4
-
11, 12
-
b19
When trying to resolve an unresolved field type, a failure (e.g. due to an incomplete class path) should be silently swallowed. Otherwise, even printing of the field becomes impossible:
Caused by: java.lang.NoClassDefFoundError
at jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.lookupType(HotSpotJVMCIRuntime.java:464)
at jdk.vm.ci.hotspot.HotSpotResolvedObjectTypeImpl.lookupType(HotSpotResolvedObjectTypeImpl.java:957)
at jdk.vm.ci.meta.UnresolvedJavaType.resolve(UnresolvedJavaType.java:92)
at jdk.vm.ci.hotspot.HotSpotResolvedJavaFieldImpl.getType(HotSpotResolvedJavaFieldImpl.java:126)
at jdk.vm.ci.meta.JavaField.format(JavaField.java:86)
at jdk.vm.ci.hotspot.HotSpotResolvedJavaFieldImpl.toString(HotSpotResolvedJavaFieldImpl.java:141)
Caused by: java.lang.NoClassDefFoundError
at jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.lookupType(HotSpotJVMCIRuntime.java:464)
at jdk.vm.ci.hotspot.HotSpotResolvedObjectTypeImpl.lookupType(HotSpotResolvedObjectTypeImpl.java:957)
at jdk.vm.ci.meta.UnresolvedJavaType.resolve(UnresolvedJavaType.java:92)
at jdk.vm.ci.hotspot.HotSpotResolvedJavaFieldImpl.getType(HotSpotResolvedJavaFieldImpl.java:126)
at jdk.vm.ci.meta.JavaField.format(JavaField.java:86)
at jdk.vm.ci.hotspot.HotSpotResolvedJavaFieldImpl.toString(HotSpotResolvedJavaFieldImpl.java:141)