On Mar 12, 10:02 am, Sean McNeil <[email protected]> wrote: > I'm not sure, but could this also be related to short enums? I seem to > remember seeing something like this when I had a mixture of old code > compiled with and new code compiled without short enums.
Everything related to DEX file access should be using the "physical" size types; by tradition u1/u2/u4/u8. Optimized DEX files are allowed to be non-portable, but the base classes.dex should not be subject to the whims of compilers (either while reading or writing). Of course, if half the code is compiled one way and half the other way, many obscure failure modes are possible. The easiest way to debug this might be to run the VM on the same core.jar on a working platform, and step through both simultaneously (either with a debugger or with logs) and identify the point where one goes off the rails. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
