On Jun 24, 2011, at 4:38 PM, Laurent Daudelin wrote:
> On Jun 24, 2011, at 15:31, Jens Alfke wrote:
>
>>
>> On Jun 24, 2011, at 3:27 PM, Laurent Daudelin wrote:
>>
>>> So, is there some way I could get more details from that mistake?
>>
>> Use NSZombieEnabled so you can find out what the over
On Jun 24, 2011, at 15:31, Jens Alfke wrote:
>
> On Jun 24, 2011, at 3:27 PM, Laurent Daudelin wrote:
>
>> So, is there some way I could get more details from that mistake?
>
> Use NSZombieEnabled so you can find out what the over-released object is.
> (Look up the name in the Xcode docs or go
On Jun 24, 2011, at 3:27 PM, Laurent Daudelin wrote:
> So, is there some way I could get more details from that mistake?
Use NSZombieEnabled so you can find out what the over-released object is. (Look
up the name in the Xcode docs or google it, if you’re not familiar with that
feature.)
—Jens
That used to work but I did some changes and I cannot find the cause of the
problem.
Basically, I'm adding an NSOperationInvocation to an NSOperationQueue.
Everything executes correctly. However, it seems that when the NSOperation is
about to exit and it's emptying its autorelease pool, it cras
