[Soot-list] About soot application class , phantom class and library class

[Steven Arzt]

Hi,

You can find an explanation here:
http://www.bodden.de/2008/08/21/soot-command-line/#app. In general, library
classes are taken from Soot's classpath. They are there, but only loaded on
demand. Application classes, on the other hand, are taken from the process
directory and are always loaded and transformed.

Phantom classes are lasses that are neither in the process directory nor on
the Soot classpath, but that are referenced by some class / method body that
Soot loads. If phantom classes are enabled, Soot will not just abort and
fail on such an unresolvable reference, but create an empty stub called a
phantom class which in turn contains phanom methods to make up for the
missing bits and pieces.

Best regards,

  Steven

 

Von: soot-list-bounces at CS.McGill.CA [mailto:soot-list-bounces at CS.McGill.CA]
Im Auftrag von jesscialuo
Gesendet: Dienstag, 15. September 2015 15:14
An: soot-list
Betreff: [Soot-list] About soot application class , phantom class and
library class

 

Hi all,

I'm not really understand the application classes , library classes,phantom
classes.Is that heros just analyze the application class ? And in what
condition,soot will treat a class as a phantom class?

And what is reachable methods ? Does it include the method in library
classes?

Thanks for your reply in advance !

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20151006/7df0ea21/attachment.html