[Soot-list] Error in Android validation/custom validation?

[Steven Arzt]

Yes, there is already an issue in the tracker. The problem is that the
validator makes assumptions that go beyond the ThrowAnalysis. The
ThrowAnalysis only defines which statement can throw which exception. The
checker however unconditionally inserts edges to capture generic exceptional
control flow with side effects - which is ok for Java, but not for Dalvik.

-----Ursprüngliche Nachricht-----
Von: soot-list-bounces at sable.mcgill.ca
[mailto:soot-list-bounces at sable.mcgill.ca] Im Auftrag von Bodden, Eric
Gesendet: Montag, 17. Februar 2014 09:40
An: Steven Arzt
Cc: Soot list
Betreff: Re: [Soot-list] Error in Android validation/custom validation?

> the ExceptionalUnitGraph assumes that the exception may occur at a
statement s, so the successor of s’ predecessor p is not s, but the
exception handler. This is a good idea in general, but for Dalvik it does
not really capture the semantics of the VM. This issue is definitely nothing
that can be fixed in a minute – otherwise I would have done it instead of
opening a bug report ^^ I hope that I will find the time to have a deeper
look into this at some point.

Hmmm... actually Soot is using a specialized ThrowsAnalysis to attempt to
handle these differences. I agree that it's not trivial to fix this but it
should be possible and we should not forget about it. But as I understand
there's already an issue for it in the tracker?

Eric