UserGuide:AnalysisScope - nimakarimipour/WALAWiki GitHub Wiki

---

wala.core technical overview

An AnalysisScope specifies the application and library code to be analyzed. [http://wala.sourceforge.net/javadocs/trunk/com/ibm/wala/util/config/AnalysisScopeReader.html#makeJavaBinaryAnalysisScope(java.lang.String,%20java.io.File) AnalysisScopeReader.makeJavaBinaryAnalysisScope()] constructs an AnalysisScope given a Java classpath String and an exclusions file (discussed further below). For more control, use the [http://wala.sourceforge.net/javadocs/trunk/com/ibm/wala/util/config/AnalysisScopeReader.html#readJavaScope(java.lang.String,%20java.io.File,%20java.lang.ClassLoader) AnalysisScopeReader.readJavaScope()] method, whose first parameter is the name of a text scope file specifying the analysis scope. A scope file has lines of the following format:

Classloader,Language,Type,Location

For Java, Classloader is one of Primordial, Extension, or Application (see Naming Java Entities). Primordial is reserved for the Java standard libraries. If you've set up your wala.properties file correctly (see Getting Started), the following two lines for Primordial should do the right thing:

Primordial,Java,stdlib,none Primordial,Java,jarFile,primordial.jar.model

Extension entries should be used for other libraries used by the application, while Application entries should be used for the application code itself. Valid values of Type are:

• classFile for a single .class file
• binaryDir for a directory containing class files (with the standard package-to-sub-directory correspondence)
• jarFile for a .jar file
• sourceFile and sourceDir for source files (for use with a Java source frontend)

Location should give the appropriate filesystem path. Here's a full example:

Primordial,Java,stdlib,none Primordial,Java,jarFile,primordial.jar.model Extension,Java,jarFile,/workspace/myapp/lib/someLib.jar Application,Java,binaryDir,/workspace/myApp/bin