[Soot-list] Tamiflex: Error in running dacapo-9.12-bach benchmark

[Sridhar Gopinath]

Hi,

I am trying to run the 'fop' and 'sunflow' programs from the dacapo-9.12-bach benchmark with Tamiflex 2.0.3 and soot-trunk. Both of the programs are giving me the same exception when trying to read from the reflection log.

java.lang.RuntimeException: Unknown method for signature: <java.awt.GraphicsEnvironment$$Lambda$1.128893786: void <init>()>
        at soot.jimple.toolkits.reflection.ReflectionTraceInfo.<init>(ReflectionTraceInfo.java:110)
        at soot.jimple.toolkits.callgraph.OnFlyCallGraphBuilder$TraceBasedReflectionModel.<init>(OnFlyCallGraphBuilder.java:215)
        at soot.jimple.toolkits.callgraph.OnFlyCallGraphBuilder$TraceBasedReflectionModel.<init>(OnFlyCallGraphBuilder.java:189)
        at soot.jimple.toolkits.callgraph.OnFlyCallGraphBuilder.<init>(OnFlyCallGraphBuilder.java:404)
        at soot.jimple.toolkits.callgraph.OnFlyCallGraphBuilder.<init>(OnFlyCallGraphBuilder.java:408)
        at soot.jimple.spark.solver.OnFlyCallGraph.<init>(OnFlyCallGraph.java:63)
        at soot.jimple.spark.builder.ContextInsensitiveBuilder.setup(ContextInsensitiveBuilder.java:73)
        at soot.jimple.spark.SparkTransformer.internalTransform(SparkTransformer.java:83)
        at soot.SceneTransformer.transform(SceneTransformer.java:39)
        at soot.Transform.apply(Transform.java:90)
        at soot.RadioScenePack.internalApply(RadioScenePack.java:57)
        at soot.jimple.toolkits.callgraph.CallGraphPack.internalApply(CallGraphPack.java:49)
        at soot.Pack.apply(Pack.java:118)
        at soot.PackManager.runWholeProgramPacks(PackManager.java:578)
        at soot.PackManager.runPacksNormally(PackManager.java:469)
        at soot.PackManager.runPacks(PackManager.java:398)
        at soot.Main.run(Main.java:271)
        at soot.Main.main(Main.java:147)
        at wpt.Main.main(Main.java:68)

The specified class is a phantom class.
I have also tried with the setting 'dontNormalize' to 'true' in poa.properties and that didn't change anything.

There is already a thread on this but there was no response:
https://mailman.cs.mcgill.ca/pipermail/soot-list/2016-March/008418.html

Can anyone please let me know the reason behind this and how to resolve it?
Thanks.

Regards,
Sridhar Gopinath,
Scalable Software Systems lab,
CSA, Indian Institute of Science,
Bangalore.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.