Thanks! I look forward to poking around, looking at how it does register allocation, etc.
For Java byte codes, I use this decompiler, which produces source code which is usually compilable: http://java.decompiler.free.fr/ It even integrates nicely into Eclipse. In my experience, it usually even does something reasonable with code that's been obfuscated with Proguard, though it can't always turn it back into Java code -- sometimes it shows you bits of disassembled byte code instead. But, to return to the original topic of this thread...you can't really prevent reverse engineering. No doubt, eventually Android will have a similar tool. But disassembly is plenty good enough to reverse-engineer things. On Mar 3, 7:16 pm, fadden <fad...@android.com> wrote: > On Mar 3, 6:09 am, Bob Kerns <r...@acm.org> wrote: > > > Re: JDASM -- that works on standard Java byte codes -- which aren't > > present on the device. Still... I don't know of one that reads > > Dalvik's byte codes, but I don't know of any reason it would be any > > harder to write. > > Try Smali:http://code.google.com/p/smali/ -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
