[Soot-list] Instrumenting Android library classes

[Steven Arzt]

Hi Peter,

 

What do you mean by „skipped“? Are you using BodyTransformers that are just not called for the Android library classes? If this is the case, you need to put them into the process-dir argument or define them as application classes. Please refer to this document for the concepts: https://ssebuild.cased.de/nightly/soot/doc/soot_options.htm#description

 

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:  <mailto:steven.arzt at ec-spride.de> steven.arzt at ec-spride.de

Web:  <http://sse.ec-spride.de/> http://sse.ec-spride.de

 

 

 

Von: soot-list-bounces at CS.McGill.CA [mailto:soot-list-bounces at CS.McGill.CA] Im Auftrag von Peter Kim
Gesendet: Montag, 15. September 2014 20:21
An: soot-list at CS.McGill.CA
Betreff: [Soot-list] Instrumenting Android library classes

 

Hi,

 

I'm trying to get Soot to instrument Android library classes, such as those in android.* packages, but such classes are not being picked up by Soot. I tried including "android.jar" and "uiautomator.jar" in "soot-classpath" option, but the library classes are still being skipped. Could you please tell me how to instrument them? Thank you.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20141009/922e29c8/attachment.html