[Soot-list] Soot Resolving Level error in FlowDroid

[Frank Liauw]

Hi All,

An update on the error will be very helpful.

Cheers

Frank

On 15 October 2014 01:20, Frank Liauw <liauw at nus.edu.sg> wrote:

> Dear Eric and Steven,
>
> Yes, I have tried it on the latest nightly build and I'm getting the same
> error, so it would seem like something from the commits between late
> September thru now broke it as I'm not observing it from the nightly build
> from late September.
>
> I am running it command line, my command is as follows:
>
> java -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC
> -Xloggc:gc.log -Xmx240g -cp
> nightly/soot-trunk.jar:nightly/soot-infoflow.jar:nightly/soot-infoflow-android.jar:nightly/slf4j-api-1.7.5.jar:nightly/slf4j-simple-1.7.5.jar:nightly/axml-2.0.jar
> soot.jimple.infoflow.android.TestApps.Test
> /Research/Apps/com.apusapps.launcher.apk
> /Research/AndroidSDK/android-sdk-linux/platforms/ --aplength 1 --nopaths
>
> The APK is as attached.
>
> Cheers
>
> Frank
>
> On 14 October 2014 08:25, Steven Arzt <Steven.Arzt at cased.de> wrote:
>
>> Hi Frank,
>>
>>
>>
>> Please report how you tried to use FlowDroid. Did you use the FlowDroid
>> classes as a library or did you run the command-line application included
>> with the tool? If you useFlowDroid in your own code, give us a minimal
>> working example. If you use the command-line tool, provide the full
>> arguments you passed to the tool. Also provide the target (APK file or JAR
>> file) on which you tried to run FlowDroid.
>>
>>
>>
>> Best regards,
>>
>>   Steven
>>
>>
>>
>>
>>
>> M.Sc. M.Sc. Steven Arzt
>>
>> Secure Software Engineering Group (SSE)
>>
>> European Center for Security and Privacy by Design (EC SPRIDE)
>>
>> Mornewegstraße 32
>>
>> D-64293 Darmstadt
>>
>> Phone: +49 61 51 16-75426
>>
>> Fax: +49 61 51 16-72118
>>
>> eMail: steven.arzt at ec-spride.de
>>
>> Web: http://sse.ec-spride.de
>>
>>
>>
>>
>>
>>
>>
>> *Von:* soot-list-bounces at CS.McGill.CA [mailto:
>> soot-list-bounces at CS.McGill.CA] *Im Auftrag von *Bodden, Eric
>> *Gesendet:* Dienstag, 14. Oktober 2014 09:09
>> *An:* Frank Liauw
>> *Cc:* soot-list at cs.mcgill.ca
>> *Betreff:* Re: [Soot-list] Soot Resolving Level error in FlowDroid
>>
>>
>>
>> Hi.
>> Do you get the same with our nightly build?
>>
>> Eric
>>
>> --
>> Sent from my mobile
>>
>> On Oct 14, 2014 3:21 AM, Frank Liauw <liauw at nus.edu.sg> wrote:
>>
>> Hi,
>>
>>
>>
>> I am trying to compile FlowDroid from source, more specifically the
>> develop branch as I am keen on trying out the memory improvements discussed
>> in
>> https://mailman.cs.mcgill.ca/pipermail/soot-list/2014-October/007420.html
>> .
>>
>>
>>
>> It compiles fine, but on running of the analysis, the following error
>> from Soot is prompted:
>>
>>
>>
>> [Call Graph] For information on where the call graph may be incomplete,
>> use the verbose option to the cg phase.
>>
>> Exception in thread "main" java.lang.RuntimeException: This operation
>> requires resolving level SIGNATURES but
>> com.android.volley.VolleyLogLog$Marker is at resolving level DANGLING
>>
>> If you are extending Soot, try to add the following call before calling
>> soot.Main.main(..):
>>
>>
>> Scene.v().addBasicClass(com.android.volley.VolleyLogLog$Marker,SIGNATURES);
>>
>> Otherwise, try whole-program mode (-w).
>>
>> at soot.SootClass.checkLevel(SootClass.java:135)
>>
>> at soot.SootClass.getMethods(SootClass.java:432)
>>
>> at
>> soot.jimple.spark.builder.ContextInsensitiveBuilder.handleClass(ContextInsensitiveBuilder.java:106)
>>
>> at
>> soot.jimple.spark.builder.ContextInsensitiveBuilder.build(ContextInsensitiveBuilder.java:85)
>>
>> at
>> soot.jimple.spark.SparkTransformer.internalTransform(SparkTransformer.java:84)
>>
>> at soot.SceneTransformer.transform(SceneTransformer.java:39)
>>
>> at soot.Transform.apply(Transform.java:90)
>>
>> at soot.RadioScenePack.internalApply(RadioScenePack.java:57)
>>
>> at
>> soot.jimple.toolkits.callgraph.CallGraphPack.internalApply(CallGraphPack.java:49)
>>
>> at soot.Pack.apply(Pack.java:116)
>>
>> at
>> soot.jimple.infoflow.android.SetupApplication.calculateCallbackMethods(SetupApplication.java:325)
>>
>> at
>> soot.jimple.infoflow.android.SetupApplication.calculateSourcesSinksEntrypoints(SetupApplication.java:265)
>>
>> at
>> soot.jimple.infoflow.android.SetupApplication.calculateSourcesSinksEntrypoints(SetupApplication.java:235)
>>
>> at soot.jimple.infoflow.android.TestApps.Test.runAnalysis(Test.java:503)
>>
>> at soot.jimple.infoflow.android.TestApps.Test.main(Test.java:208)
>>
>>
>>
>> How do I go about resolving this error? It did not come up when I'm using
>> the nightly build from late September. I came across another issue at
>> https://mailman.cs.mcgill.ca/pipermail/soot-list/2014-July/007068.html
>> which references a similar problem.
>>
>>
>>
>> Any guidance will be much appreciated.
>>
>>
>>
>> Thank you!
>>
>>
>>
>> Frank LIAUW
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20141023/00f21c34/attachment.html