NSZombieEnabled hides EXC_BAD_ACCESS error entirely

Posted by David Liu on Stack Overflow See other posts from Stack Overflow or by David Liu
Published on 2010-04-21T18:14:39Z Indexed on 2010/04/21 19:33 UTC
Read the original article Hit count: 353

Filed under:
|
|
|
|

So I have a subclass of a UIView that starts causing EXC_BAD_ACCESS errors when I go through a specific set of conditions (run on iPad instead of iPhone or simulator, first login only). It throws the exception when the UIView subclass gets deallocated, during the last line, where I have [super dealloc]. I heard about using NSZombieEnabled, so I tossed that on to see if I could get any more information about it, but now it hides the error completely!

Does anyone know a bit more about this type of situation? I thought NSZombie would start spewing stuff into my console like before, but I'm hoping that the nonexistance of errors would tell me some sort of information as well.

© Stack Overflow or respective owner

Related posts about iphone

Related posts about objective-c