Android debug tools

Mohsen,

It depends what types of problems you are looking to debug and at what level (ie, kernel, bootloaders, Ducati, Android, etc).  Here is a list of the main tools that we use to debug issues with Android on OMAP.  (Of course, there are many many other tools and techniques available, including many open source Linux utilities.)

- Print statements - printk's, early printk's, RAM console (/proc/last_kmsg), logcat, Ducati prints

- omapconf - very powerful tool for easily accessing registers and debugging power management issues

- Software tracers - ftrace, GDB, SystemTap

- Memory debugging - mtest, TILER memory map, mtrace (only for Linux, not Android), Valgrind

- Profilers - grabserial, top, oprofile

- JTAG / Lauterbach

Several of these topics are described more in detail on omappedia.  Let me know if there is a particular issue that you are trying to solve, and I can try to help guide you to the best debug techniques.

Regards,
Gina 

Gina

what we are after is more like Android application debug. My customer might move from Windows embedded to android so they are worried about what kind of tools are available to debug android stuff. that is why the question is coming up. With embedded windows all the tools are integrated and easy to use. But i am not sure what we have for Android. The guys in the Sitara group had a bunch of stuff with CCS but sounds like you guys dont use CCS for android debug.

If you can point me to anything that i can start to read or understand what tools we ahve for the android debug that would be great.

Thanks

Mohsen