CoreAnimation call from UIKit causing mysterious crash - Printable Version
+- iDevGames Forums (http://www.idevgames.com/forums)
+-- Forum: Development Zone (/forum-3.html)
+--- Forum: Tools & Technology (/forum-10.html)
+--- Thread: CoreAnimation call from UIKit causing mysterious crash (/thread-10186.html)
CoreAnimation call from UIKit causing mysterious crash - funkboy - Jul 20, 2012 12:43 PM
I have some basic animation in an iOS app I'm creating that has behaved completely fine... until yesterday.
I apparently made a change that somehow affected it, and I'm having trouble identifying what the issue is.
When stepping through the code, it gets to this chunk of code, and dies after stepping over the commitAnimation line (I originally wrote this before I realized the beauty of [UIView animateWithDuration: ...]:
The error from the debugger after I step over commitAnimation is giving me very little help:
Does anyone know what kind of array this might be talking about? It is a UIKit call that it's dying on, so I'm thinking the array is some array of views used by UIKit, but that I have no visibility into...
Any ideas on how to address or even further investigate this would be great!
RE: CoreAnimation call from UIKit causing mysterious crash - OneSadCookie - Jul 20, 2012 02:52 PM
A symbolicated backtrace would be useful, not just the hex addresses!
RE: CoreAnimation call from UIKit causing mysterious crash - funkboy - Jul 21, 2012 03:28 PM
So... I will fully admit my stupidity and what I have learned.
When stack traces are not symbolicated, there are a LOT of ways to handle it... and I was not handling it all before. I was just going, "oh crap, I have no stack trace... shucks."
Thank you to this answer:
There's even a slick catch-all Exception Breakpoint in Xcode that can help a lot with problems like this.
With this knowledge, I should have no problem solving this.
So hopefully this thread can help even one newbie (of which I didn't consider myself.. until just now, ugh) know that undecipherable code stack traces in the Xcode debugger can be easily fixed!