Previous frame inner to this frame (gdb could not unwind past this frame)-iPhone/Cocos2d

[GoogleCodeExporter]

Strange bug, using the Box2d template with 0.8.2 build of cocos2d for the 
iphone.  After a while, 
(but not every time) the simulator locks up and the error in the log of: 


...
2009-10-23 22:58:07.314 Castle[12599:20b] Add sprite 273.00 x 230
[Session started at 2009-10-23 22:58:17 -0500.]
GNU gdb 6.3.50-20050815 (Apple version gdb-967) (Tue Jul 14 02:11:58 UTC 2009)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-apple-darwin".sharedlibrary apply-load-rules 
all
Attaching to process 12599.
Previous frame inner to this frame (gdb could not unwind past this frame)
Previous frame inner to this frame (gdb could not unwind past this frame)
kill
quit

The Debugger has exited with status 0.


The error happens for me about 5% of the time, and seems more likely right when 
a box is 
added.  It also seems to be more likely to happen with more boxes (never seen 
it with less than 
20).  I have never caught it on debug on actually hardware, but I have 
experienced the lock.

I have put trace comments in all over the place, and cannot find where it is 
happening that way, 
but removing the world->step seems to eliminate the error.  I have tried to run 
with guard 
malloc on to find memory issues, but alas it will not crash with guard malloc 
on.  I have tried 
fixed framerate, no help.   

Original issue reported on code.google.com by drk...@gmail.com on 24 Oct 2009 at 4:59

[GoogleCodeExporter]

Can you reproduce this in Visual Studio in the testbed? I cannot support ports.

Original comment by erinca...@gmail.com on 20 Nov 2009 at 7:54

• Changed state: Invalid