[Soot-list] Soot Dacapo Issue

[Eric Bodden]

Hi Tong.

All classes should be replaced if all classes are, in fact, also loaded on your second run. Are both runs functionally equivalent?

Cheers
Eric

> On 8. Feb 2019, at 01:20, Zhou, Tong <tz at gatech.edu> wrote:
> 
> Hi Eric,
> 
> Thanks a lot! That worked! Sorry I am a little confused about the pia agent. So when I used pia to do a relay run, even if I don't specify the loading directory ("inDir"), it still report 857 classes are replaced. The second question is that when I do point "inDir" to transformed class directory, the new added replaced classes are less than the total number classes in the "inDir" directory. Shouldn't every class be used? Are some of them not loaded? Thanks!
> 
> -Tong
> 
> From: Eric Bodden <eric.bodden at uni-paderborn.de>
> Sent: Wednesday, February 6, 2019 5:03 AM
> To: Zhou, Tong
> Cc: soot-list at CS.McGill.CA
> Subject: Re: [Soot-list] Soot Dacapo Issue
>  
> Hi again.
> 
> Yes there’s the option -no-bodies-for-excluded, see here:
> https://soot-build.cs.uni-paderborn.de/public/origin/develop/soot/soot-develop/options/soot_options.htm
> 
> It forces Soot to load JimpleBodies only for classes that are included in the command line. (see Application Mode Options in the same document)
> Non-loaded classes are then represented as Phantom Classes with empty method bodies.
> 
> Hope that helps!
> 
> Best wishes
> Eric
> 
> > On 5. Feb 2019, at 19:39, Zhou, Tong <tz at gatech.edu> wrote:
> > 
> > Hi Eric,
> > 
> > Thanks for the reply! I was just wondering if Soot has a mode such that it only tries to resolve the classes on the command line and does not try to resolve classes referenced by these classes. Thanks!
> > 
> > -Tong
> > From: Eric Bodden <eric.bodden at uni-paderborn.de>
> > Sent: Monday, February 4, 2019 3:48 AM
> > To: Zhou, Tong
> > Cc: soot-list at CS.McGill.CA
> > Subject: Re: [Soot-list] Soot Dacapo Issue
> >  
> > Hi Tong.
> > 
> > Can you be more specific? What’s the error you are seeing? And what’s the exact command line?
> > 
> > Eric
> > 
> > > On 2. Feb 2019, at 00:31, Zhou, Tong <tz at gatech.edu> wrote:
> > > 
> > > Hi,
> > > 
> > > I am trying to follow the tutorial from https://github.com/Sable/soot/wiki/Using-Soot-and-TamiFlex-to-analyze-DaCapo, but ran into an error. 
> > > 
> > > I first ran "java -javaagent:poa-x.y.z.jar -jar dacapo-9.12-MR1-bach.jar avrora" and that dumped some classes in "out/" (dumped classes). But when I tried to run Soot on these dumped classes, Soot had difficulty resolving classes that are not dumped but referenced by the dumped classes. I also tried "-allow-phantom-refs", and that couldn't fix it either. Both "out/" and dacapo.jar were in Soot's class path. Anyone know how to fix this? I just wanted to run Soot just on the argument classes, without having to resolve all referenced classes. Either suppressing this resolving or fixing it works for me. Thanks! 
> > > 
> > > -Tong
> > > 
> > > _______________________________________________
> > > Soot-list mailing list
> > > Soot-list at CS.McGill.CA
> > > https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
> > 
>