My code compiles but bombs whenever I click on the button Start Game. Before I added all the code in my game file, when I clicked Start Game it transitioned fine.
After the code compiles I get an error at the bottom of the screen:
Error from Debugger: mi_cmd_stack_list_frames: Not enough frames in stack.
What does this mean and how do I fix it???
*The only thing I know is that the error is from the game file*
*Additionally I have four warnings*
My code compiles but bombs whenever I click on the button Start Game. Before I added all the code in my game file, when I clicked Start Game it transitioned fine.
After the code compiles I get an error at the bottom of the screen:
Error from Debugger: mi_cmd_stack_list_frames: Not enough frames in stack.
What does this mean and how do I fix it???
*The only thing I know is that the error is from the game file*
*Additionally I have four warnings*
Try doing a "clean all" from the "build" menu. Might be an xcode/gdb bug.
Also, try to fix the other warnings - it could be a side affect of those warnings.
The "clean all" did not work. I will try to fix the warnings.
Before the frame error comes up, it says GDB: Program received signal: "EXC_BAD ACCESS."
After this my frame stacks load and it says the error I said earlier.
"EXC_BAD ACCESS" is the problem - that's what you usually get when you try to access an object and it isn't there - usually because you didn't initialize it, or because you released it and it was destroyed (dealloc'd). Follow PD's advice and step through the code.
"EXC_BAD ACCESS" is the problem - that's what you usually get when you try to access an object and it isn't there - usually because you didn't initialize it, or because you released it and it was destroyed (dealloc'd). Follow PD's advice and step through the code.
How do you "set a breakpoint in the action method that's executed when you tap the button."
How do you "set a breakpoint in the action method that's executed when you tap the button."
Click the blue/gray area to the left of the line you want to stop on. A dark blue arrow will appear.
The next time you build-and-go, the program will stop on that line (actually, just before running that line.) The red arrow shows you the next line that will be run. Then you can roll over variables to see what they contain while the program is running.
Use the "continue" button just above the editor to continue execution. Drag the breakpoint out of the breakpoint area to remove it.
i had a table view in IB and i connected the datasource and delegate to my object. I didnt have any data yet to fill it and that gave me the SIGABRT error for some reason. I unconnected the DataSource for my table view and that caused the error to leave.
Perhaps the frame problem is that he's running out of memory on his device. I get this error on my 8GB iPod when I accidentally leave all of the NSZombie* & MallocStack* argument flags enabled from a debug session in the simulator - the RAM on the iPod is not enough to handle all of that data.