The tools to process and view these files are not shipped with the current SDK. So , the native tracing isn't supported in the SDK yet. You can only use the method tracing for now.
On Wed, Jun 18, 2008 at 1:56 AM, Horia <[EMAIL PROTECTED]> wrote: > > Hello, > > The emulator and API provides a couple of ways of tracing and > profiling your applications: > 1. the android.os.Debug provides some methods like: > startMethodTracing(), startNativeTracing() > 2. the emulator could be run with "-trace" option in order to later > accept the start tracing command (F9) > > The problem is nativeTracing (started by F9 or startNativeTracing() > method) generates some files I don't know how to use: > qtrace.bb > qtrace.exc > qtrace.pid > qtrace.method > qtrace.inst > qtrace.static > > Does anyone know how can I view the contents of these files ?(they are > binaries, not ascii) > > Thanks! > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
