I’ve noticed that if you call a selector on an object that doesn’t support that selector (e.g. viewDidLoad on a NSView) during [NSViewController viewDidLoad] the exception causes the view or window to silently fail to draw and you get a window with no content. This can be frustrating to track down, and certainly quite mystifying the first time! As this sort of thing has happened to me a couple of times, I wonder if there is some sort of reporting mechanism (e.g. an env variable) that I could enable which would put Cocoa in a verbose mode that would report on such things, or better yet get Xcode to halt the program when an undefined selector is used on a valid object?
Alternatively, is there a guide to advanced cocoa debugging tips available somewhere?
