Re: How does one break on _NSKVODeallocateLog?
Re: How does one break on _NSKVODeallocateLog?
- Subject: Re: How does one break on _NSKVODeallocateLog?
- From: John Stiles <email@hidden>
- Date: Thu, 6 Sep 2007 10:48:32 -0700
If you can reproduce the problem on demand, try setting breakpoints
on printf, fprintf, and NSLog, then get the error to occur. Most
likely you will get a full stack trace, including the full name of
the function in question.
On Sep 6, 2007, at 10:34 AM, David Hoerl wrote:
One of my objects is observing my NSWindowController subclass.
Running in "Debug" mode, when the controller closes I see this
message:
... An instance 0x494a90 of class IVWindowController is being
deallocated while key value observers are still registered with it.
Break on _NSKVODeallocateLog to start debugging.
So I tried a a breakpoint on "_NSKVODeallocateLog", and one on
"[NSWindowController _NSKVODeallocateLog]", but neither worked.
I googled "_NSKVODeallocateLog" and got a few hits, one of which
was an earlier post here for info on this breakpoint.
Sure would be nice if someone could respond to this (for the
archives) and tell the world how one does in fact break on this error.
Thanks!
David
PS: I tracked down the problem so this is purely for future reference.
_______________________________________________
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:
40blizzard.com
This email sent to 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