Steven Arzt
Steven Arzt
Have a look at ``InfoflowConfiguration.sootIntegrationMode``. There is an option ``UseExistingCallgraph``.
Your sequence of calls is correct. You set the correct flag before calling ``runInfoflow``. There is only one Soot instance. The wording is misleading. Essentially, FlowDroid can create a new...
After the callgraph has been constructed, you can call ``Scene.v().getCallGraph()`` to access the callgraph data structure.
To visualize the callgraph, you can simple iterate over the callgraph and write the edges into a [dot](https://en.wikipedia.org/wiki/DOT_(graph_description_language)) file. There are tools for rendering dot files as images. The different...
The method source should normally be set by the Soot resolver. Have you tried the Stubdroid option to load the entire JAR just to be safe that you're not missing...
The current development version of FlowDroid depends on a refactoring from the current Soot development branch. You'll need to build Soot from source as well, or use the last official...
Before you try to build FlowDroid using, e.g., ``mvn package``, clone the [Soot repository](https://github.com/soot-oss/soot) and run ``mvn install`` on it.
Make sure that you have a JDK, not only a JVM.
That's an interesting one. If we had the implementation of ``setClass()`` as part of the Jimple code, the ``StrongUpdatePropagationRule`` would kill the taint on the respective inner field of the...
The access path itself only denotes a piece of data on stack (variable) or heap (sequence of field dereferences). I think this is generic enough so that we don't need...