On May 10, 2016, at 16:43 , Roland King <[email protected]> wrote:
>
> Well no he hasn’t
Correct … no he hasn’t. I mis-edited a longer draft of the post.
> Now that I've changed things over to use the context value, I get this at the
> moment I add an NSOperation to the NSOperationQueue:
>
> [uploadQueue addOperation:opn]; <-- Thread 1, EXC_BAD_ADDRESS (code=1,
> address=0xc)
>
> (lldb) po uploadQueue
> <NSOperationQueue: 0x17e76d20>{name = 'Upload Queue'}
>
> (lldb) po opn
> <NSInvocationOperation: 0x17de5890>
>
> (lldb) bt
> * thread #1: tid = 0x207807, 0x204e3a86 libobjc.A.dylib`objc_msgSend + 6,
> stop reason = EXC_BAD_ACCESS (code=1, address=0xc)
> frame #0: 0x204e3a86 libobjc.A.dylib`objc_msgSend + 6
> frame #1: 0x2151e27e Foundation`-[NSObject(NSKeyValueObservingPrivate)
> _changeValueForKeys:count:maybeOldValuesDict:usingBlock:] + 278
> frame #2: 0x214822d0 Foundation`-[NSObject(NSKeyValueObservingPrivate)
> _changeValueForKey:key:key:usingBlock:] + 68
It’s in the middle of handling a change notification. I’d suggest setting a
breakpoint at the top of your ‘observeValueForKeyPath:…’ method.
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
