From: Dave Howell <groups@...>
Date: 2006-01-13T18:52:05+09:00
Subject: Re: Advanced rubycocoa: full-screen applications? (Can I access CoreGraphics calls?)


> However, I'm having another problem.  My application is crashing, and  
> the error is somewhere in the Ruby libraries, not directly in my code.  
>  Here's the program output:
>
> 2006-01-10 03:31:04.506 NRFApp[918] NRFView(0x60dba0) - NSView not  
> correctly initialized. Did you forget to call super?
> 2006-01-10 03:31:04.531 NRFApp[918] QCView(0x60e870) - NSView not  
> correctly initialized. Did you forget to call super?
> /Users/merc/Documents/Development/thingmagic/NRFApp/build/Development/ 
> NRFApp.app/Contents/Frameworks/RubyCocoa.framework/Versions/A/ 
> Resources/ruby/osx/objc/oc_wrapper.rb:17: [BUG] Bus Error
> ruby 1.8.2 (2004-12-25) [powerpc-darwin8.2.0]
>
>
> NRFApp has exited due to signal 6 (SIGABRT).
>
> Another run went like this:
>
> [Session started at 2006-01-10 03:31:42 -0500.]
> Current time is: Tue Jan 10 03:31:42 2006
>
> 2006-01-10 03:31:42.993 NRFApp[932] NRFView(0x60daf0) - NSView not  
> correctly initialized. Did you forget to call super?
> 2006-01-10 03:31:43.063 NRFApp[932] QCView(0x60e7c0) - NSView not  
> correctly initialized. Did you forget to call super?
> /Users/merc/Documents/Development/thingmagic/NRFApp/build/Development/ 
> NRFApp.app/Contents/Frameworks/RubyCocoa.framework/Versions/A/ 
> Resources/ruby/osx/objc/oc_wrapper.rb:17: [BUG] Segmentation fault
> ruby 1.8.2 (2004-12-25) [powerpc-darwin8.2.0]
>

Aha! Hopefully you will soon have a more complete answer, but I guess  
you missed my recent query which featured exactly the same "NSView"  
error message.

Or to be more precise, the warning. "Did you forget to call super?" is  
a red herring, a spurious message that you should ignore. My views, as  
it turned out, were being created exactly as they should have been.

The incredibly exasperating Segmentation Fault is another matter, of  
course. I had to put one Ruby XCode project aside entirely because I  
couldn't get that to go away. However, at first, many of those were to  
some degree my fault. I had some bugs in my code where I was calling  
something without initializing it properly, or, well, I don't remember  
what, but it was actually a mistake that I had made, which  
Ruby/RubyCocoa/Cocoa was handling with extremely poor grace.

Until/unless somebody more knowledgeable than me chimes in, I suggest  
you see if you can find some particular part of your code that seems to  
trigger the segmentation fault, and make sure it's doing what it's  
supposed to. If that doesn't help, consider upgrading your Ruby (and  
especially your RubyCocoa if you're not running the latest version).