I’ve been trying to tackle this crash and just don’t know where to begin. Can someone help me figure out how to use Xcode’s tools to navigate this information properly to find the culprit? I don’t even know what these details are:
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve been trying to tackle this crash and just don’t know where to begin. Can someone help me figure out how to use Xcode’s tools to navigate this information properly to find the culprit? I don’t even know what these details are:
The Instruments tool should be your first port of call – particularly the leaks and allocations analyser.
To use it, select the
Profileoption off the Product menu in Xcode.You might like to investigate using the
NSZombieobject which is designed to catch over-releasing of objects.It may of course be that you’re simply passing a pointer to something that is not a Core Foundation/Cocoa object where one is expected.