If your app is being downloaded by other people and crashing on remote devices, you may want to look into an Android error reporting library (referenced in this SO post). If it's just on your own local device, you can use LogCat. Even if the device wasn't connected to a host machine when the crash occurred, connected the device and issuing an adb logcat command will download the entire logcat history (at least to the extent that it is buffered which is usually a loooot of log data, it's just not infinite). Do either of those options answer your question? If not can you attempt to clarify what you're looking for a bit more?

您还可以为它使用整个(简单的)服务，而不仅仅是库。我们公司刚刚为此发布了一项服务:http://apphance.com。

It has a simple .jar library (for Android) that you add and integrate in 5 minutes and then the library gathers not only crash information but also logs from running application, as well as it lets your testers report problems straight from device - including the whole context (device rotation, whether it is connected to a wifi or not and more). You can look at the logs using a very nice and useful web panel, where you can track sessions with your application, crashes, logs, statistics and more. The service is in closed beta test phase now, but you can request access and we give it to you very quickly.

声明:我是Polidea的CTO，也是这项服务的共同创建者。

如果你想立即得到答案，你可以使用logcat

$adb shell logcat -f /sdcard/logoutput.txt *:E

如果您的日志中现在有太多垃圾，请先尝试清除它们。

$adb shell logcat -c

然后尝试运行您的应用程序，然后再次logcat。

您也可以尝试[BugSense]原因:垃圾邮件重定向到另一个url。BugSense收集并分析所有崩溃报告，并为您提供有意义的可视化报告。它是免费的，而且只需要一行代码就可以进行集成。

声明:我是联合创始人

我是Bugsnag的创始人之一，我们正是为此目的而设计的。Bugsnag自动捕获Android应用程序中未处理的异常，并将它们发送到我们的仪表板，在那里您可以优先修复并深入诊断信息。

以下是在选择或构建崩溃报告系统时需要考虑的一些重要事项，以及一些代码片段:

自动检测未处理的异常(示例代码) 收集诊断数据，如内存使用情况、设备信息等(示例代码) 根据根本原因有效地将崩溃组合在一起 允许您跟踪用户在每次崩溃前采取的操作，以帮助重现(示例代码)

如果你想在Android上看到一些关于崩溃处理/报告的最佳实践，你可以查看Bugsnag的崩溃报告库的完整源代码，它是完全开源的，可以自由地把它拆开，并在你自己的应用程序中使用!

We use our home-grown system inside the company and it serves us very well. It's an android library that send crash reports to server and server that receives reports and makes some analytics. Server groups exceptions by exception name, stacktrace, message. It helps to identify most critical issues that need to be fixed. Our service is in public beta now so everyone can try it. You can create account at http://watchcat.co or you can just take a look how it works using demo access http://watchcat.co/reports/index.php?demo.