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.
In the second paragraph from the bottom of this post on reading crash logs the author mentions adding labels to the methods so that you can clearly see which task caused the crash.
How do you do this? Mind you I’m talking about C and Objective-C within XCode for the iPhone.
Thanks!
Eric, what that article is referring to are the symbols of the application.
When you build a binary with Xcode, specifically for Archiving/Release, Xcode will create a separate “folder file” called YourAppName.dSYM.
The dSYM file is essentially a big list of memory addresses and the function/method calls in your application that correspond to them.
Any crash log you view in Xcode should then automatically go from memory addresses to symbols based on that DSYM file.
However, when you get a crashlog from iTunes Connect or from another user directly, you’ll need to use
symbolicatecrashon the command line to do this. There are plenty of tutorials out there on this.