Re: Tracking a EXC_BAD_ACCESS when zombies don't work

On Wed, 16 Feb 2011 11:17:27 -0800, Keith Blount said: >The debugging continues... You could try valgrind too: It works decently on Mac OS now (though no Obj-C GC support still)... -- Sean McBride

Re: Tracking a EXC_BAD_ACCESS when zombies don't work

aced all of the code and the problem document that seemed to be triggering the crash into the separate app... And of course it refused to crash. The debugging continues... Thanks again! All the best, Keith --- On Wed, 2/16/11, Bruce Cresanta wrote: > From: Bruce Cresanta > Subject: Re

Re: Tracking a EXC_BAD_ACCESS when zombies don't work

A big clue is in your backtrace: #261968 0x98d06f38 in CFRelease #261969 0x98d06f38 in CFRelease #261970 0x98d06f38 in CFRelease #261971 0x98d33c6d in _CFAutoreleasePoolPop #261972 0x9867d0aa in NSPopAutoreleasePool #261973 0x9867cfd2 in -[NSAutoreleasePool drain] #261974 0x986c4596 in _NSAppleEve

Re: Tracking a EXC_BAD_ACCESS when zombies don't work

, 2/15/11, Sean McBride wrote: > From: Sean McBride > Subject: Re: Tracking a EXC_BAD_ACCESS when zombies don't work > To: "Keith Blount" , cocoa-dev@lists.apple.com > Date: Tuesday, February 15, 2011, 8:55 PM > On Tue, 15 Feb 2011 12:41:51 -0800, > Keith Blount s

Re: Tracking a EXC_BAD_ACCESS when zombies don't work

On Tue, 15 Feb 2011 12:41:51 -0800, Keith Blount said: >I'm trying to debug an EXC_BAD_ACCESS crash in my application and am >tearing my hair out trying to find the cause. I have NSZombieEnabled set >to YES, but this isn't providing me with any information (using >NSZombieEnabled is always one of

Tracking a EXC_BAD_ACCESS when zombies don't work

Hello, I'm trying to debug an EXC_BAD_ACCESS crash in my application and am tearing my hair out trying to find the cause. I have NSZombieEnabled set to YES, but this isn't providing me with any information (using NSZombieEnabled is always one of the first things I try with crashes like this one