Xcode error at runtime: "EXC_BAD_ACCESS"

#1 EXC_BAD_ACCESS

This error is simply saying its trying to access a null pointer. Step through the code at that point and see what exactly its trying to access. When you have found what it is, its normally missing datablocks, or missing files (cos it doesnt make dsos ON the device, as suggested.) EXC_BAD_ACCESS = null pointer

#2 Thanks Dale. I tried loading up the behavior shooter and it gives the same error! So there must be something wrong with my Xcode project and not my game.

#3 Ah, i see. It might be that the resources/dependencies arent being compiled?? what i found is to right click on the "common" folders INSIDE of xcode, and say compile.

ps : its FuzzY , not dale :P

#4 I restored my Xcode project from the iTGB 1.1 download and the EXC_BAD_ACCESS error on loading has gone away - however I now get one when I quit the game! When I press the home button the game freezes (with the music looping about half a second of audio) and Xcode shows another EXC_BAD_ACCESS error.

Also, when I launch the game from the iPod by pressing the icon, it displays the loading screen (default.png) and then quits back to the home screen.

#5 thats weird, if you have the device connected to XCode, find the console. The itge might not be able to print to the console.log file, but the console is still printed to debug in xcode, allowing you to read whats happening at run time. You can real time debug which is real nice on mobile, try breaking at "onShutdown" or the end of load level, etc... stepping through each line checking whats up

#6 I didn't realise you could view the console when running on the device. How is that done?

#7 Using the GDB output window. You need to call enableDebugOutput( true ); somewhere in your game, and form then on it'll output.

#8 Sigh - my 'fix' was a false alarm. The game is only running when I run it in debug mode. When I switch to release mode it fails on startup with EXC_BAD_ACCESS still.

The Debugger console shows:

TGBGame_Optimize1 : -missing2 : -this
performing mainInit()
Program received signal: "EXC_BAD_ACCESS".

It's not even getting to the stage where it begins to run any torquescript.

In Debug mode it is loading ok and the TGB console is echoing to the debugger window, but it's around 10 frames per second slower, so not much good for real tuning.

#9 If it runs OK in simulator, but crashes on the device, it's more than likely using too much memory.

mainInit() is where it starts all the Torque systems(platform, input, console, etc..) if I recall correctly, so one of them might be having a fatal error, you might check which one doesn't init properly.

#10 Thanks Mat. The game is only 6Mb in total so it's unlikely to be a memory issue.

If I run it on the simulator in release or debug mode I get "Error from Debugger: Failed to launch simulated application: Unknown error."

It only runs on hardware in debug mode.

My game runs fine on Windows and Mac in iTGB.

#11 Reinstalled Xcode, iPhone SDK and iTGB and now it works ok in release mode. phew!

#12 glad to hear it, and to clear something up , when the device runs out of memory you can know by the error status 101 on exit

#13 I just got this error too.... the only thing I did was $pref::iPhone::enableMultipleTouch = true; from false. I am going to see if I can build in release mode like mentioned above, bug maybe with enabling multitouch?