CODEWITHSUNDEEP
iphoneobjective-cxcodedebugging
Moshe
Moshe

Reputation: 58097

More than just EXC_BAD_ACCESS?

Is there a more detailed error to be found other than the console's EXC_BAD_ACCESS? Where/how can I see it?

When my app crashes, I see the error in thE XCode status bar, but the console shows nothing else. Where do I see more info about what causes the crash?

Upvotes: 0

Views: 195

Answers (1)

heckj
heckj

Reputation: 7367

The application will have a stack trace, typically in the crash logs. Definitely look there for a bit more detail. Look under ~/Library/Logs/CrashReporter for those details. In general, run the application "Console.app" in your Utilities folder, and click on the button "Show Log List". It gives a detailed view into all the logs available that you'd likely want to check out in your system

If it's code you have written, the debugger (gdb) is the "how" to go to look for more detail. That's typically a "you overreleased" some object if you're working in Objective-C. There's a good set of notes on using the technique "NSZombieEnabled" to find what you're blowing up on.

Upvotes: 3

Related Questions