On Thu, Mar 12, 2009 at 10:13 AM, vkat <[email protected]> wrote: > Also I ran dexdump and it does not show any errors. Seeing the code > for dexdump, it dumps only the class details (optionally the > classdefs). As far as I understood the code, it was not parsing the > type list.
That's why I said "dexdump won't print out the entire contents of the file in general" and indicated how to get a full dump (which will require building core.jar not just copying it). > Also is there a standard procedure to build for glibc (one earlier > posting talked about "lunch 2", but I think it is now not supporting > glibc). I don't build for the desktop myself, so I'm afraid I don't know off- hand what the right way to do so is, these days. Sorry. > Also as another experiment, I pulled the optimized cache file from > emulator /data/dalvik-cache/sys...@framework@[email protected] I wouldn't expect an optimized dex file to run other than on the platform it was specifically built for. There are lots of interdependencies baked into those. Basically, you're probably making it a bit further into running the system because optimized dex files get run without performing the verification done on unoptimized files (since they were presumably verified before getting turned into optimized dexes). And the verification on unoptimized files on your system demonstrates that there is a real problem, somewhere. -dan --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
