Strange EXC_BAD_ACCESS problem

[frankmail007]

My app encountered a EXC_BAD_ACCESS error and app crash (no other information at console at all). I found some tutorials about how to deal with this kind of problem. So I add NSZombieEnabled environment variable and set it to YES. But the strange thing happened. The app don't crash anymore and there is nothing useful in console. After I remove this variable, the app crash again.

I know it must be something wrong in memory management. But how can I debug the problem?

[dany_dev]

Originally Posted by frankmail007

My app encountered a EXC_BAD_ACCESS error and app crash (no other information at console at all). I found some tutorials about how to deal with this kind of problem. So I add NSZombieEnabled environment variable and set it to YES. But the strange thing happened. The app don't crash anymore and there is nothing useful in console. After I remove this variable, the app crash again.

I know it must be something wrong in memory management. But how can I debug the problem?

reading a book. or posting the code.

[Duncan C]

Originally Posted by frankmail007

My app encountered a EXC_BAD_ACCESS error and app crash (no other information at console at all). I found some tutorials about how to deal with this kind of problem. So I add NSZombieEnabled environment variable and set it to YES. But the strange thing happened. The app don't crash anymore and there is nothing useful in console. After I remove this variable, the app crash again.

I know it must be something wrong in memory management. But how can I debug the problem?

Make sure you are using a debug build of your app, and run it in XCode using the "Build and debug" menu option (command Y)

EXEC_BAD_ACCESS is almost always an over-released object, so zombies is the right tool to find it.

[god0fgod]

Also check the stack to learn where the error was made. That can help.

[Duncan C]

Originally Posted by god0fgod

Also check the stack to learn where the error was made. That can help.

Unfortunately, with over-released objects the stack track is not usually useful. By the time the crash occurs, the source of the over-release is usually long gone.

[god0fgod]

It's worth a look, if it doesn't take you to the problem straight away it gives you vital clues and you can trace the problem back to the source.

[frankmail007]

The problem is there is nothing in stacks and console although I'm running the program in debug and NSZombieEnabled is set to YES.

But anyway, I solved the problem. I accidentally put [super alloc] before other object's release.

Thank you all anyway.