A fast, easy to use, free, and community supported 2D game engine
Ever since i went to xcode 4, the assert behavior is to log an error on the console and then "restart" the thread. The result is you dont know where the break happens if you don't happen to have the console up and it usually just keeps asserting over and over and over if its on the run loop.
Has anyone else seen this or know a solution? It used to suspend as if it hit a breakpoint.
I've seen the same behavior in xcode 3. The best I could figure it out is that if the assert happens on a non-main thread or as a result of a ui gesture event, the debugger just kills the thread but keeps running. I don't have a good solution. When in need, I converted:
NSAssert(condition, @"message")
Into:
if (!condition)
NSAssert(false, @"message");
And just put a break point on the assert line.
it can happen on any thread. I was stepping through my code which was from a scheduler tick and suddenly the code jumped somewhere entirely different. On the console I see the assert and the thread started over again. So annoying. I think I may have to replace all asserts in cocos with my own function call so i can put the breakpoint in a single place. if(!<assert condition>){myErrorFunc(@"msg"); something like that.
I have talked to some other people that also have this problem so its not isolated at least.
You must log in to post.
