Thank you for the additional information. I will look into it later. One thing that kept me from further working with this a few days ago is that I ran the monkey tool with the --hprof option, which according to http://code.google.com/intl/zh-TW/android/reference/monkey.html puts results in the data/misc folder. However, it seems impossible (prohibited) to access that folder on the phone to retrieve the generated profiling results? So can this only be used by people who flash their own phones with a development build, or did I overlook something (I did not dig for long)?
Thanks On Feb 3, 1:24 am, fadden <fad...@android.com> wrote: > > Unfortunately I don't have a lot of different compilers to test with. > <stdint.h> is only needed for a couple of types (uint8_t and > uint32_t); not sure if there's a better way to deal with those. I > figured variadic macros could be a problem, but since it's a debug > macro that is compiled out by default I figured at worst people could > just strip it out entirely. > > One user reported some problems running it under Cygwin that sounded > like stdin/stdout were undergoing text conversion, so I posted a new > version that takes the input and output files as arguments, and will > fopen them with "rb"/"wb". Per UNIX convention, you can specify "-" > to use stdin/stdout for the original behavior. (I probably should've > done it this way in the first place.) > > New version is up onhttp://bigflake.com/HprofConv.c.txt. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
