On Sep 30, 2012, at 11:38 AM, Kyle Sluder wrote:
> On Sun, Sep 30, 2012, at 10:57 AM, Lee Ann Rucker wrote:
>> Weird that you didn't get the warning, but we've switched to the pattern
>> of
>>
>> [self addObserver:self forKeyPath:@"ctrl.selectedObjects.someString"...
>>
>> and that's saved coun
On Sun, Sep 30, 2012, at 10:57 AM, Lee Ann Rucker wrote:
> Weird that you didn't get the warning, but we've switched to the pattern
> of
>
> [self addObserver:self forKeyPath:@"ctrl.selectedObjects.someString"...
>
> and that's saved countless headaches. You can remove your own observers
> in dea
Weird that you didn't get the warning, but we've switched to the pattern of
[self addObserver:self forKeyPath:@"ctrl.selectedObjects.someString"...
and that's saved countless headaches. You can remove your own observers in
dealloc so you never need to worry about when to remove the observer.
--
On 9/29/12 3:40 PM, Ken Thomases wrote:
I sympathize. It can be very hard to debug these sorts of things.
A couple of things I would try:
1) Examine the registers for the stack frame of the objc_msgSend_vtable5()
call to see if you can figure out what message was being sent and possibly
its ar
