Steven Arzt

That doesn't seem to be a FlowDroid issue, but rather a problem with Soot. Does it happen on a specific APK only or on all APKs? How much memory (heap...

The two implementation are fundamentally different. The ``CFGViewer`` simply interate over all classes in the app and prints out the intra-procedural control flow for each method. Your sample program with...

I can't reproduce the issue. It would be great if someone who has this problem could debug it and propose a fix as a merge request.

That's a tricky one. When a project has a proper license, it usually (GPL, LGPL, Eclipse, etc.) defines that derived works are allowed, but only under the condition that the...

Here's the list of contributors: - Steven Arzt (TU Darmstadt and Fraunhofer SIT) - Siegfried Rasthofer (TU Darmstadt and Fraunhofer SIT) - Julian Schütte (Fraunhofer AISEC) - Eric Bodden (TU...

If you are using the FlowDroid JAR with dependencies, it might simply be compiled against a different version of Soot. Did you compile FlowDroid on your own? When running Soot,...

There is a solution for the original problem in this thread, i.e., remove the exclusion. This thread has nothing to do with JAR files. Please do not mix topics.

Are you sure that your Android platform directory is correct? It must point to the ``platforms`` directory inside your Android SDK. If that's not the problem, please post your entire...

The platfom directory must contain subdirectories for the individual platform JARs. So you keep the original folder structure from the Android SDK? You may not point to an invidual JAR,...

You can use the ``PreAnalysisHandler`` to inject code instrumentation into the analysis (have a look at ``SetupApplication.addPreprocessor()``). The access paths have nothing to do with the instrumentation part.