ios - Handling hidden errors Objective C -


We've all come across clear errors and complex errors. I'm currently programming an iPad app several times Which are really hard to track down. Even when using

  NSUncaughtExceptionHandler ();   

And many other error handling calls My question is that when you try all the obvious techniques to track an error, and you crash the app for no apparent reason What are the best advances and what are the best error handling techniques?

Console output

  Current language: Auto; At present, the error of killing A-C while hitting the goal (kill anyway): Warning: "Source / () / (OS / Kern) Failure (0x5x) Exited with exit code of the program: 0    

this debugger is crashing / error, not your app

though , It is possible that some rails have been closed in your app, causing the debugger to be useless.

You may be corrupted or for example, for example Withdrawal from memory.

Along with that, the latest devices are up-to-date because the debugger usually has a bug fix that enables it to behave better in the face of CrashFlik inferior failure. .

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -

python - referencing a variable in another function? -