Re: Problem with NSOperation exiting and crashing the app
Re: Problem with NSOperation exiting and crashing the app
- Subject: Re: Problem with NSOperation exiting and crashing the app
- From: Laurent Daudelin <email@hidden>
- Date: Fri, 24 Jun 2011 15:38:17 -0700
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 google it, if you’re not familiar with that feature.)
>
> —Jens
Hey Jens.
I forgot to mention that I did enable NSZombieEnabled with a bunch of breaks in .gdbinit:
set env NSDeallocateZombies=NO
set env MallocCheckHeapEach=100000
set env MallocCheckHeapStart=100000
set env MallocScribble=YES
set env MallocGuardEdges=YES
set env MallocCheckHeapAbort=1
set env CFZombie 5
fb -[_NSZombie init]
fb -[_NSZombie retainCount]
fb -[_NSZombie retain]
fb -[_NSZombie release]
fb -[_NSZombie autorelease]
fb -[_NSZombie methodSignatureForSelector:]
fb -[_NSZombie respondsToSelector:]
fb -[_NSZombie forwardInvocation:]
fb -[_NSZombie class]
fb -[_NSZombie dealloc]
But no luck! It still crashes in:
#0 0x7fff870bff10 in objc_msgSend
#1 0x7fff838b2206 in _CFAutoreleasePoolPop
#2 0x7fff8268fff3 in -[__NSOperationInternal start]
#3 0x7fff8276dc59 in ____NSOQSchedule_block_invoke_2
#4 0x7fff80d95d64 in _dispatch_call_block_and_release
#5 0x7fff80d742d1 in _dispatch_worker_thread2
#6 0x7fff80d73c08 in _pthread_wqthread
#7 0x7fff80d73aa5 in start_wqthread
-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin http://www.nemesys-soft.com/
Logiciels Nemesys Software email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden