Re: Too many @selector statements?
Re: Too many @selector statements?
- Subject: Re: Too many @selector statements?
- From: Christoffer Lernö <email@hidden>
- Date: Sun, 2 Oct 2005 10:33:18 +0200
On Oct 2, 2005, at 09:34 , John C. Randolph wrote: That looks like the crash happens when trying to post the notification. I would make sure in gdb that at runtime that methods for those selectors exist in the observer's class. addObserver:selector:name:object: doesn't check whether the given observer implements the selector.
It was even simpler. The story is that I ran this as a testcase using UnitKit, which wasn't going through the debugger so I couldn't really check what was happening at runtime. The thing crashed because I failed to remove some observers before deallocating them. Since what notifications got tested varied with the order the test-cases ran, I got this odd behaviour.
Thanks for pushing me in the right direction.
/Christoffer |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden