I don't know if this is a known issue or what. I remember that failed assertions used to stop the program, which was very good. Now I have seen that only error message is displayed in the console, over and over again, depending on the assert. Right now I have for example "Assertion failure in -[CCSprite setTexture:], /Users/janischulze/Documents/tode_27_01_2010/cocos2d/CCSprite.m:819", because I have probably defined animation that uses frames from other spritesheets than the actual sprite is. The actual assertion is correct, the problem is that my game in the simulator is frozen and my console is flooding with those assertions.
Is there a way to ensure that running the program ends at this point so I can see backtrace in debugger?
