Static Public Methods | |
void | analyze () |
void | analyze (SootClassManager sootClassManager, Collection storedClasses) |
void | compile (String classPath, LinkedList classNames, LinkedList packageNames) |
void | main (String[] args) |
void | reset () |
Static Private Methods | |
void | dumpFile (String outputPath) |
void | printUsage () |
Static Private Attributes | |
boolean | dump = false |
SootClass | rootSootClass |
SootMethod | rootSootMethod |
Collection | storedClasses = null |
SootClassManager | sootClassManager = null |
CallBackRegistry | callbackReg = new CallBackRegistry() |
Definition at line 74 of file BOFA.java.
|
Analyzes the loaded classes. This interface can be used analyze a set of classes which are "jimplified" using soot directly.
|
|
Analyzes the classes that are available through JJJC.
It is assumed that the
Definition at line 154 of file BOFA.java. Referenced by analyze(), and main().
|
|
Compiles the given java classes using JJJC.
Definition at line 223 of file BOFA.java. Referenced by main().
|
|
Outputs the Jimple representation of all classes available through the class manager.
Definition at line 272 of file BOFA.java. Referenced by main().
|
|
Entry point to BOFA in stand alone mode. Currently nothing is displayed after the analysis. It provides an assurance of whether the analysis went along fine or failed.
|
|
Safe exit in case of wrong usage in command line mode. Definition at line 367 of file BOFA.java. Referenced by main().
|
|
Resets the complete Analysis engine. All collected data are destroyed. |
|
Central registry of callbacks. Such callbacks are used to alter the flow graph.
One possible way is to add callbacks to hook the |
|
Indicates whether the Jimple files of the analyzed class should be dumped or not. |
|
Class in the code from where the analysis will commence. |
|
Method in the rootSootClass from where the analysis will commence. |
|
|
|
Collection of classes to be analyzed. This should include all classes which can be reached from the given classes. |