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 running into an EXC_BAD_ACCESS bug and have been racking my brain trying to figure out the solution. I believe I know the issue but I can’t narrow down the line that it’s happening on and the debug log isn’t helping me. I’ve embedded the crash log below. If anybody could help me figure out how to track things down I’d be extremely grateful! I have turned on NSZombieEnabled but that is not giving me any additional information.
text is better than a screenshot, but I think I can read that screen.
the crash is in your code at 0x1000. You’ll want to sybolicate that: Symbolicating iPhone App Crash Reports
the frames in libobjc are most likely because you are passing a bogus pointer to objc_msgSend(); something that looks enough like a pointer that objc tries to poke at the garbage value is if it were an object.
this isn’t necessary an over-release problem; could just be a trashed pointer / trashed memory.
You can probably disassemble the binary and figure out what symbols is that the address listed. Or something pretty close.
otoolis your friend.nmmight be, too. But… proper symbolication is far superior.