cocos2d: my APP crashes but XCode doesn't give me any crash report

Question

It used to work fine but now I get this message when loading a certain scene and then the APP crashes.

2012-12-01 18:33:55.104 AppName[9561:707] cocos2d: CCSpriteFrameCache: Trying to use file 'art1-hd.png' as texture

I have no idea on where to start debugging this. Is there a way to get a more precise error message to understand why this happens?

Btw, I have changed my code signing identity to developer and XCode doesn't yet give me any trace of it on the console other than the plain message above. I checked as well the device logs on the Xcode-Organizer section but no trace.

I whish there was something like in Java + Eclipse, where I could get a precise STACKTRACE of where the crash happened.

Any suggestion on how to get a precise stacktrace (E.g. with function name generating the crash)?

PS: I have set strip debug symbols to "NO" in DEBUG, and to "YES" in Release, but I am builing on my own test iPod and hence I think it is automatically build for "Debug" (the section says build for running and testing which is confusing as the project settings allows only debug and release). But I think the problem is not here.. but in the issues above before the PS:

EDIT: If I look into the debug navigator I don't see any stacktrace of methods, as I want, but just threads.. I need to figure out how to use the global exceptions.

If the console message is a result of an exception being thrown by cocos2d then you may get a better result by setting a breakpoint on Objective-C exceptions in the Breakpoint Navigator. — Phillip Mills, Dec 02 '12 at 18:19
You forgot to sensor the name of your app in the Xcode activity display, and the Xcode scheme selector. ;) — Jasarien, Dec 04 '12 at 14:47

score 0 · Answer 1 · edited May 23 '17 at 12:27

0

I have no idea on where to start debugging this.

You have the cocos2d source code. I would start there.

Search for "trying to use file" in CCSpriteFrameCache to understand what the cause of this message is (which I agree is confusing, why shouldn't you use that file?).

As for the stack trace, it's available as soon as you add a global exception breakpoint. If the breakpoint triggers in OpenAL code make sure to set it to catch only Objective-C exceptions.

edited May 23 '17 at 12:27

Community

1
1

answered Dec 03 '12 at 09:16

CodeSmile

64,284
20
132
217

Hi Steffen, I added an EDIT whit what I get.. I don't manage to figure out how to find the method call stacktrace. – mm24 Dec 04 '12 at 14:04

cocos2d: my APP crashes but XCode doesn't give me any crash report

1 Answers1