"EXC_BAD_ACCESS" with empty stack trace in simulation
Posted: Fri Nov 18, 2011 6:17 am
Hello to all,
I am developing an app based on Cocos2d+Chipmunk for iOS and I am experiencing random crashes during the simulation. Now, the bad part is that the stack trace that Xcode is showing is empty. This is GDB output to the bt command:
(gdb) bt
#0 0x00000000 in ?? ()
I am really at a loss here as to what could be causing the fault. I understand this is a matter of some pointer going NULL before its life ends, but due to the empty stack I have no idea about which op was last attempted.
The simulation can run any time from 5 secs to several minutes, but in the end it crashes. I am not getting any low memory warning; the app runs fine collision after collision until it crashes.
I am not at all meaning that this is a bug in Chipmunk, rather I am looking for a suggestion as to how to go about such case, where I have a crash, in the middle of a simulation, with an empty stack trace, so that I have really no clue about where to start from.
Which parts of Chipmunk could I "attack" with log traces or breakpoints in order to understand what is happening?
Thank you very much for your help!
Sergio
I am developing an app based on Cocos2d+Chipmunk for iOS and I am experiencing random crashes during the simulation. Now, the bad part is that the stack trace that Xcode is showing is empty. This is GDB output to the bt command:
(gdb) bt
#0 0x00000000 in ?? ()
I am really at a loss here as to what could be causing the fault. I understand this is a matter of some pointer going NULL before its life ends, but due to the empty stack I have no idea about which op was last attempted.
The simulation can run any time from 5 secs to several minutes, but in the end it crashes. I am not getting any low memory warning; the app runs fine collision after collision until it crashes.
I am not at all meaning that this is a bug in Chipmunk, rather I am looking for a suggestion as to how to go about such case, where I have a crash, in the middle of a simulation, with an empty stack trace, so that I have really no clue about where to start from.
Which parts of Chipmunk could I "attack" with log traces or breakpoints in order to understand what is happening?
Thank you very much for your help!
Sergio