处理隐藏的错误目标C. [英] Handling hidden errors Objective C

问题描述

我们都遇到了明显的错误和复杂的错误。我目前正在编写一个iPad应用程序。有几次我遇到了很难找到的错误。即使使用

We have all come across obvious errors and complicated errors. I am currently programming an iPad app. A couple of times I have come across errors that are really quite hard to track down. Even when using

NSUncaughtExceptionHandler();

以及各种其他错误处理调用。我的问题是，当你尝试了所有显而易见的技术来追踪错误时，你的应用程序正在崩溃，没有明显的原因。最好继续，最好的错误处理技巧是什么？

and a variety of other error handling calls. My question is when you have tried all the obvious techniques to track down an error, and you app is crashing for no apparent reason. Hows best to proceed and what are the best error handling techniques?

控制台输出

Current language:  auto; currently objective-c
kill
error while killing target (killing anyway): warning: error on line 2184 of    "/SourceCache/gdb/gdb-1708/src/gdb/macosx/macosx-nat-inferior.c" in function "void macosx_kill_inferior_safe()": (os/kern) failure (0x5x)
quit
Program ended with exit code: 0

推荐答案

这是调试器崩溃/错误，而不是你的应用程序。你无法在应用程序中执行任何操作。

That is the debugger crashing / erring, not your app. Nothing you can do in the app cam catch that.

但是，您的应用程序中的某些内容可能已经脱轨，导致调试程序发生故障。

However, it is likely that something in your app has gone off the rails, causing the debugger to freak out.

例如，您可能正在破坏或内存不足。

You might be corrupting or running out of memory, for example.

此外，更新最新工具的日期因为调试器通常会有错误修复，使其在遇到灾难性的低级故障时表现得更好。

Also, up date to the latest tools as the debugger will typically have bug fixes that make it behave better in the face of catastrophic inferior failure.

这篇关于处理隐藏的错误目标C.的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！