On Apr 13, 7:21 pm, Sahil Arora <[email protected]> wrote: > (1) what is the size of code that actually goes inside the mobile phone to > the DVM??
The entire DEX file is installed on the device. It's memory-mapped. How much actually winds up in physical memory depends on how many of the classes and methods are actually used. > (2) secondly, is it possible to know how much is the size of Code Segment, > Data Segment, Stack, Heap are affected by adding some new functionalities in > your application?? Code size + data size changes can be observed by looking at the size of the DEX file. Stack and heap are runtime changes, and are tricky to determine by simply looking at the DEX (heap moreso than stack). DDMS provides some information on heap usage. > (3) Thirdly, since u seem to be more accustomed to dexdump command, so, can > u please let me know what are the things that u would see in a dexdump file. dexdump displays much of the data in the DEX file. To understand what it means, see the dex format documentation in dalvik/docs/dex- format.html in the source tree. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
