ปกติผมใช้ log.d นะครับ แต่ยังมีอีกหลายวิธีเลย ลองอ่่านดูครับ
Top Debugging Tips
Dump the stack trace
To obtain a stack dump from emulator, you can log in with adb shell, use “ps” to find the process you want, and then “kill -3 “. The stack trace appears in the log file.
Display useful info on the emulator screen
The device can display useful information such as CPU usage or highlights around redrawn areas. Turn these features on and off in the developer settings window as described in Setting debug and test configurations on the emulator.
Get system state information from the emulator (dumpstate)
You can access dumpstate information from the Dalvik Debug Monitor Service tool. See dumpsys and dumpstate on the adb topic page.
Get application state information from the emulator (dumpsys)
You can access dumpsys information from the Dalvik Debug Monitor Service tool. See dumpsys and dumpstate on the adb topic page.
Get wireless connectivity information
You can get information about wireless connectivity using the Dalvik Debug Monitor Service tool. From the Device menu, select “Dump radio state”.
Log trace data
You can log method calls and other tracing data in an activity by calling startMethodTracing(). See Running the Traceview Debugging Program for details.
Log radio data
By default, radio information is not logged to the system (it is a lot of data). However, you can enable radio logging using the following commands:
adb shell
logcat -b radio
Capture screenshots
The Dalvik Debug Monitor Server (DDMS) can capture screenshots from the emulator. Select Device > Screen capture.
Use debugging helper classes
Android provides debug helper classes such as util.Log and Debug for your convenience.
อ้างอิงจาก
http://developer.android.com/guide/developing/debug-tasks.html
