[Soot-list] Soot RuntimeException
Eric Bodden
bodden at st.informatik.tu-darmstadt.de
Mon Dec 20 11:41:58 EST 2010
Hi Jochen.
> analyzing source code I got the following exception:
>
> Exception in thread "Thread-3" java.lang.RuntimeException: couldn't find
> class: wildcards.& java.lang.Class<wildcards.? extends ij.ImageJ>&
> java.lang.Class<wildcards.? extends ij.ImageStack> (is your
> soot-class-path set properly?)
> at soot.SootResolver.bringToHierarchy(SootResolver.java:184)
> at soot.SootResolver.bringToSignatures(SootResolver.java:219)
> at soot.SootResolver.bringToBodies(SootResolver.java:260)
> at soot.SootResolver.processResolveWorklist(SootResolver.java:135)
> at soot.SootResolver.resolveClass(SootResolver.java:124)
> at soot.Scene.loadClass(Scene.java:425)
> at soot.Scene.loadClassAndSupport(Scene.java:410)
> at soot.Scene.loadNecessaryClass(Scene.java:1010)
> at soot.Scene.loadNecessaryClasses(Scene.java:1024)
> at soot.Main.run(Main.java:167)
> at soot.Main.main(Main.java:141)
I am unsure. This may be a bug in the JastAdd frontend, or it may be
the case that you are indeed missing some classes.
> If I switch to the polyglot frontend (-polyglot) it gets even worse (is
> the polyglot frontend designed for Java 1.5? I know that thete is
> polyglot version that supports Java 1.5 but I don't know wheather this
> verison is used in soot)
The polyglot frontend cannot cope with Java 5 syntax.
Would it be possible for you to analyze bytecode?
Eric
More information about the Soot-list
mailing list