现在Firebase崩溃报告非常流行，也更容易使用。 详情请参考以下连结: Firebase崩溃报告

希望对你有所帮助。

这是非常野蛮的，但是可以在任何地方运行logcat，所以一个快速而肮脏的hack是在任何捕获块中添加getRuntime()。Exec ("logcat >> /sdcard/logcat.log");

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?

谷歌Play开发者控制台实际上为你提供了那些已经崩溃和发送报告的应用程序的堆栈跟踪，它也有一个非常好的图表来帮助你查看信息，参见下面的例子:

我一直在Android和iOS应用中使用cratercism——我在techcrunch上听说过它们。到目前为止，他们都很满意!

好吧，我看了rrainn和Soonil提供的样本，我找到了一个解决方案 这不会破坏错误处理。

我修改了CustomExceptionHandler，以便它从我们关联的新线程中存储原始的UncaughtExceptionHandler。在新的“uncaughtException”的末尾- 方法，我只是使用存储的UncaughtExceptionHandler调用旧函数。

在DefaultExceptionHandler类中，你需要这样的东西:

public class DefaultExceptionHandler implements UncaughtExceptionHandler{
  private UncaughtExceptionHandler mDefaultExceptionHandler;

  //constructor
  public DefaultExceptionHandler(UncaughtExceptionHandler pDefaultExceptionHandler)
  {
       mDefaultExceptionHandler= pDefaultExceptionHandler;
  }
  public void uncaughtException(Thread t, Throwable e) {       
        //do some action like writing to file or upload somewhere         

        //call original handler  
        mStandardEH.uncaughtException(t, e);        

        // cleanup, don't know if really required
        t.getThreadGroup().destroy();
  }
}

在http://code.google.com/p/android-remote-stacktrace上对代码进行了修改 你有一个很好的工作基地，登录到你的web服务器或 sd卡。