exc-bad-access
UIScrollView EXC_BAD_ACCESS crash in iOS SDK
I just worked through this problem myself. I had an issue where: A scrollview delegate was wired to a UIViewController The scrollview began animating The delegate went away and dealloc was called. The problem was the scrollview delegate messages were firing on a new-deallocated object, and the crash logs were a bit confusing as they … Read more
EXC_BAD_ACCESS code 2 on UIAlertView in iOS6
I’ve got it. I have the same problem, in my case it seems that the method is thrown from background now (now in ios7, in ios6 UIAlertView was automatically put into the main-thread as @nodepond says -thanks!-).. try to assure that the method is shown from main thread: [alertView performSelectorOnMainThread:@selector(show) withObject:nil waitUntilDone:YES]; Good luck!
Break on EXC_BAD_ACCESS in Xcode?
For any EXC_BAD_ACCESS errors, you are usually trying to send a message to a released object. The BEST way to track these down is use NSZombieEnabled. This works by never actually releasing an object, but by wrapping it up as a “zombie” and setting a flag inside it that says it normally would have been … Read more
Post of NSNotificationCenter causing “EXC_BAD_ACCESS” exception
One of your subscribers has been deallocated. Make sure to call [[NSNotificationCenter defaultCenter] removeObserver:self] in your dealloc (if not sooner).
What’s the meaning of exception code “EXC_I386_GPFLT”?
EXC_I386_GPFLT is surely referring to “General Protection fault”, which is the x86’s way to tell you that “you did something that you are not allowed to do”. It typically DOESN’T mean that you access out of memory bounds, but it could be that your code is going out of bounds and causing bad code/data to … Read more