NSString *it = @”blah”;
NSLog(@”only one parameter ‘%@’ dummy %@”, it);

which was causing the EXC_BAD_ACCESS.

But the debugger kept pointing me to some other random locations. I basically worked backwards commenting out things until I narrowed down the real cause.

yeah EXC_BAD_ACCESS is quite an issue
I have 4 posts about different cases you might have happening, have a look here :

http://www.touch-code-magazine.com/?s=EXC_BAD

If all else fails … go old school – put a breakpoint somewhere before the code fails and step trough the code to see what’s going on man

Marin

This is really useful information. Unfortunately, I have not found my problem. I enabled zombies and all I see in the debugger is EXC_BAD_ACCESS.

I know I’ve enabled it correctly because I purposely created an over released scenario. In my “fake” case I get a message like:
*** -[MyObject retainCount]: message sent to deallocated instance 0×6682380

Any thoughts on how to debug this further?

Ruug

- Joe

This is very useful piece of information.
I, too, spent many hours finding the problem and fixed it under a minute with NSZombies.

Just found this page after hours of fighting with an EXC_BAD_ACCESS bug and unsuccessfully trying to find where it was happening. Like Sreejit, read this, enabled NSZombie and almost instantly found the problem.

Thanks for the help.

Pete

great you had it solved and did left me feedback Totally what makes me write on this site!

Marin

Thanks for this post. It helped me a lot. A LOT. I had been struggling with the EXEC_BAD_ACCESS for almost 4 hours before looking to this post (via google) . I solved the bug within a couple of minutes after enabling NSZombieEnabled.

Thanks a lot.

-Sreejit