<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"&\#24494";
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        mso-believe-normal-left:yes;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.E-MailFormatvorlage18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
        {page:WordSection1;}
--></style><![if mso 9]><style>p.MsoNormal
        {margin-left:7.5pt;}
</style><![endif]><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple style='margin-left:7.5pt;margin-top:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt'><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>You can find an explanation here: <a href="http://www.bodden.de/2008/08/21/soot-command-line/#app">http://www.bodden.de/2008/08/21/soot-command-line/#app</a>. 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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> Steven<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> soot-list-bounces@CS.McGill.CA [mailto:soot-list-bounces@CS.McGill.</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>CA] <b>Im Auftrag von </b>jesscialuo<br><b>Gesendet:</b> Dienstag, 15. September 2015 15:14<br><b>An:</b> soot-list<br><b>Betreff:</b> [Soot-list] About soot application class , phantom class and library class<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt'><span style='font-size:10.5pt;font-family:"&#24494","serif";color:black'>Hi all,<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt;text-indent:24.0pt'><span style='font-size:10.5pt;font-family:"&#24494","serif";color:black'>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?<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt;text-indent:24.0pt'><span style='font-size:10.5pt;font-family:"&#24494","serif";color:black'>And what is reachable methods ? Does it include the method in library classes?<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin:0cm;margin-bottom:.0001pt;text-indent:24.0pt'><span style='font-size:10.5pt;font-family:"&#24494","serif";color:black'>Thanks for your reply in advance !<o:p></o:p></span></p></div></div></div></body></html>