|
|
| Line 176: |
Line 176: |
|
| |
|
| == Advanced Debugging == | | == Advanced Debugging == |
| | Beyond just using Android logcat, there are other options for debugging Firefox for Android, depending on your needs. |
|
| |
|
| === Using logcat === | | === Logcat apps ==== |
| | |
| [http://developer.android.com/guide/developing/tools/logcat.html logcat] is a tool that is going to show you some logs prompted by the device. It might be a good help if you don't want to or can't run gdb. You can use it by running this command:
| |
| | |
| adb logcat -v time
| |
| | |
| You can make things appear in logcat using printf_stderr. With debug builds, NS_WARNING, NS_ERROR and NS_ASSERTIONS will show up in logcat. If you're trying to debug something, you may wish to pipe the logcat output through grep to filter out irrelevant things (most Fennec-related output will be viewable by
| |
| | |
| adb logcat -v time | grep Gecko
| |
| | |
| but remember that when attaching log output to a bug you should include unfiltered output as there may be relevant log entries under other tags.
| |
| | |
| ==== Using other logcat apps ====
| |
| ===== ICS (4.1) and below ===== | | ===== ICS (4.1) and below ===== |
| * Install the [https://market.android.com/details?id=org.jtb.alogcat&hl=en aLogCat] app. Use it to capture logs and attach the logs to bugs. | | * Install the [https://market.android.com/details?id=org.jtb.alogcat&hl=en aLogCat] app. Use it to capture logs and attach the logs to bugs. |