[Soot-list] What transformer changes static invokes?

[Steven Arzt]

Hi Marc-André,

Please send me the JAR / APK file you are analyzing and a full (non-truncated) stack trace, ideally one that happens when running the Soot command-line application or a minimal working example.

Best regards,
  Steven

-----Ursprüngliche Nachricht-----
Von: soot-list-bounces at CS.McGill.CA [mailto:soot-list-bounces at CS.McGill.CA] Im Auftrag von Marc-André Laverdière
Gesendet: Mittwoch, 26. November 2014 04:03
An: soot-list at sable.mcgill.ca
Betreff: [Soot-list] What transformer changes static invokes?

Hello everybody,

I've been having a weird bug today -
soot.ResolutionFailedException: Resolved
<fr.unice.i3s.modalis.jSeduite.technical.image.registry.PictureAlbumRegistryCRUD:
java.lang.String toSql(java.util.Date)> to
<fr.unice.i3s.modalis.jSeduite.technical.image.registry.PictureAlbumRegistryCRUD:
java.lang.String toSql(java.util.Date)> which has wrong static-ness
 	at soot.SootMethodRefImpl.checkStatic(SootMethodRefImpl.java:114)
 	at soot.SootMethodRefImpl.resolve(SootMethodRefImpl.java:129)
 	at soot.SootMethodRefImpl.resolve(SootMethodRefImpl.java:109)
 	at
soot.jimple.internal.AbstractInvokeExpr.getMethod(AbstractInvokeExpr.java:67)

What's interesting is that javap tells me that, inside that class, toSql is _always_ called with invokestatic.

What transformer could be doing this? How can I disable it? I am running this within Flowdroid, so some default could be set that I'm not aware of.

That class is resolved at level BODIES and it is _not_ phantom.

--
Marc-André Laverdière-Papineau
Doctorant - PhD Candidate
_______________________________________________
Soot-list mailing list
Soot-list at CS.McGill.CA
https://mailman.CS.McGill.CA/mailman/listinfo/soot-list