Closed pettermahlen closed 9 years ago
This seems to be a case of the following byte code being issued:
LDC LSomeClass;.class
INVOKEVIRTUAL java/lang/Class.getCanonicalName ()Ljava/lang/String;
LDC with a symbolic reference to a class causes that class to be resolved, and it's that resolution that's failing. We should possibly/probably add checks for that kind of class resolution.
I haven't got the exact example in front of me, but it was similar to:
The
SomeClass.class.toString()
invocation throws a NoClassDefFoundError becauseSomeClass
fails to load since the interface is not on the class path.