On Oct 31, 2:18 pm, strazzere <[EMAIL PROTECTED]> wrote: > I've been doing some research on dexdump and it helps out > tremendously. [...] > Though it is old, however I'm not exactly sure how this author find > out what "vtable #00**" means. > > Is there any documentation on dexdump or these values?
Documentation for the DEX format and Dalvik instructions can be found in dalvik/docs/ in the git repository. The documentation does not describe the implementation of the "-quick" instructions, which are substituted into the instruction stream by "dexopt". For general information about dexopt, see dalvik/docs/ dexopt.html. The vtable index is simply an index into the table of methods defined for that class. The order in which methods appear is dependent upon the contents of the superclass (which might be in a different DEX file) and the exact behavior of the VM, so generally speaking there's no reliable way for dexdump to translate that back to a method signature. (The first 11 or so come out of java.lang.Object, and you can make educated guesses about the rest based on argument types, but it's an uphill battle.) You're generally better off examining the un-optimized APK file. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
