一对夫妇更多的事情，以确保：

A couple more things to ensure:

• 挂起全部设置为
• 在通知：
  • 的捕捉到异常的，如果被抓到有错误处理的定义有例外
  • 的未捕获的异常的，如果没有被处理的异常都被捕获
  • Suspend set to all
  • Notifications on:
    • Caught exception if exceptions that have error handling defined are to be caught
    • Uncaught exceptions if exceptions that are not handled are to be caught

    在这里看到更详细的说明：http://***.com/a/28862538/3063884

    See more detailed instructions here: http://***.com/a/28862538/3063884

    

    该方法捕获了复活（当'抓'和'未捕获被选中），所有异常。因此，所有的内部异常升高。一类滤波器的规范排除一些例外的规定，本。例如，在屏幕上方倾倒，在 ClassNotFoundException的，这是在启动过程中经常提出的，将被忽略。

    This approach catches all exceptions that are raised (when 'caught' and 'uncaught' are checked). Thus all internal exceptions are raised. The specification of a class filter restricts this by excluding some of these exceptions. For example, in the screen-dump above, the ClassNotFoundException, which is raised frequently during start-up, is ignored.

    有一个小缺点这种方法是，在应用程序启动时，有可能是一条消息，表明无法找到当前栈帧源类。这是因为不是所有的源$ C ​​$ C已被加载。这在启动期间将只发生一次，并且可以安全地忽略。另一种方法，以避免这种情况（是否有在应用程序启动时预期也不例外）是'运行'应用程序（而不是开始调试），然后通过的运行的手动附加应用程序的调试器 - >的连接调试到Android的过程的......或者pressing的按钮在工具栏中。

    A small downside of this approach is that during app start-up, there may be a message indicating "Cannot find source class for current stack frame". This is because not all of the source code has been loaded yet. This will only occur once during start-up and can safely be ignored. An alternative approach to avoid this (if there are no exceptions expected during app start-up) is to 'Run' the application (as opposed to starting 'Debug'), and then manually attach the app to the debugger via Run -> Attach debugger to Android process ... or by pressing the button in the toolbar.