-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APUT_OBJECT changed to APUT #20
Comments
Might be related to the Google Keep phi issue... |
Hopefully fixed in d6a7530. It was a very silly one as I treated null reference as Integer type. After this fix that test apk is throwing another exception which I think is related to some instrumenting code. |
Great! Looks like it's working! |
Yes it is the native println thing, in which case I'll close this issue. |
The Test_ArrayPut_NULL class contains the following method:
Recompilation (with instrumentation), however, changes the array instruction to simple 'aput', which makes the class fail verification... Instrumentation doesn't change the instruction at all - simply wraps it with TRY/CATCH and adds one more instruction after, so it must be the compiler thinking that
v0
is an integer. CodeAnalyzer correctly analyzes the code before instrumentation, as theconst/4 v0, 0x0
instruction is correctly instrumented as NULL.Test APK:
https://www.dropbox.com/s/jpj37evl1nigos1/Dexter_Issue20.apk
The text was updated successfully, but these errors were encountered: