[Soot-list] Analyse a scala project using soot

[Bernhard Berger]

Hi,

this message is indeed a little bit confusing since there are two different class paths. The class path referred in the output is not your Java classpath.  You have to adjust the soot classpath (the second -cp argument) to contain all the dependencies used in the application you are analyzing (the same way you have to provide it to java if you want to run the application). Alternatively you can use the --allow-phantom-refs parameter if you do not have the libraries at hand. Normally it is the better decision to adjust your class path.

Regards, Bernhard  

> Am 06.02.2017 um 11:02 schrieb Pooja Agrawal <poojaagrwl at cse.iitb.ac.in>:
> 
> Hi,
> 
> I want to analyse and optimize a Scala project by doing static analysis using soot framework, same as we do for java project. Since Scala code generates java bytecode on compilation, I thought it would be easy to generate jimple representation and I can add my transformations. But I am not able to get even a correct jmple representation. Can you please share the details and also I want to know whether it is possible to decompile a jimple code back into Scala like java?
> The errors are kind of
> " couldn't find class: scala.reflect.ScalaSignature " or  " couldn't find class: org.apache.spark.api.java.JavaRDD ",
> although I set the soot-classpath same as mentioned in the tutorial.
> I am attaching the screenshot of my terminal also.
> 
> 
> Regards,
> Pooja Agrawal
> ------------------<errors.png>_______________________________________________
> Soot-list mailing list
> Soot-list at CS.McGill.CA
> https://mailman.CS.McGill.CA/mailman/listinfo/soot-list