[Soot-list] Implication of include-all in whole-program mode

[Manas Thakur]

Yes, this was helpful. Thanks.

Regards,
Manas

> On 24-May-2016, at 3:52 PM, Steven Arzt <Steven.Arzt at cased.de> wrote:
> 
> Hi Manas,
> 
> The "include-all" and "app mode" options are completely orthogonal to whether you enable whole program mode or not. Include-all means that no classes will be excluded by default, not even internal stuff like sun.*. App mode means that all classes on the Soot classpath are treated as application classes, so everything is loaded and transformed. This so far only tackles inputs.
> 
> Whole program mode takes whatever your inputs are and then runs transformers that not only look at a body at a time, but at the whole scene. You need it for algorithms such as callgraph computation. It does not define what the scene includes or treats as application or library classes.
> 
> I hope this clarifies the concepts a bit.
> 
> Best regards,
>  Steven
> 
> -----Ursprüngliche Nachricht-----
> Von: soot-list-bounces at CS.McGill.CA [mailto:soot-list-bounces at CS.McGill.CA] Im Auftrag von Manas Thakur
> Gesendet: Dienstag, 24. Mai 2016 08:13
> An: soot-list at CS.McGill.CA
> Betreff: [Soot-list] Implication of include-all in whole-program mode
> 
> Hello all,
> 
> What happens when I add or do not add “include-all” in whole-program mode? The command-line options webpage describes it only for “app” mode; however, I could observe the number of potential callees at a JDK call-site to decrease if I do not give “include-all” in whole-program mode as well.
> 
> Regards,
> Manas
> _______________________________________________
> Soot-list mailing list
> Soot-list at CS.McGill.CA
> https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
>