[Mono-osx] OS X 10.5?

[Andrew Ayre]

Thanks Curtis,

removing base.awakeFromNib solved the problem for one 10.5.8 machine but
now it crashes on start up on a different 10.5.8 machine:

Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c01461e7
Crashed Thread:  0

Looks like somewhere in the AppKit but it's hard to tell. Nothing
recognizable in the crash info... :(

I guess MonoMac cannot be used reliably on 10.5.

Andy

On 10/4/2011 12:26 PM, Curtis Wensley wrote:
> Also, found this:
> 
> http://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Protocols/NSNibAwaking_Protocol/Reference/Reference.html
> 
> Specifically, this excerpt:
> 
> 
>> You should call the super implementation of awakeFromNib only if you know
>> for certain that your superclass provides an implementation. Because the
>> Application Kit does not provide a default implementation of the
>> awakeFromNib method, calling super results in an exception if the parent
>> class does not implement it. Classes whose immediate parent class is
>> NSObject or NSView do not need to call the super implementation. For any
>> other classes, you can use the instancesRespondToSelector: class method of
>> NSObject to determine if the parent class responds to awakeFromNib and
>> call the method if it does.
>>
> 
> Perhaps you should not be calling the base class after all?  or at least use
> the RespondsToSelector to see if it actually is implemented in the base
> class..
> 
> 
> --
> View this message in context: http://mono.1490590.n4.nabble.com/OS-X-10-5-tp3857825p3872073.html
> Sent from the Mono - OSX mailing list archive at Nabble.com.
> _______________________________________________
> Mono-osx mailing list
> Mono-osx at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-osx
> 
> 
> 

-- 
Andy
PGP Key ID: 0xDC1B5864