Puts $RUBYCOCOA_DEBUG = true in your app somewhere and have a look at
the output, that should give you more of a pointer to what's actually
going wrong.
Cheers,
Chris
On 29 Nov 2007, at 17:28, Pierce T. Wetter III wrote:
>
> So I've had a crashing bug in rubycocoa upon starting my app from
> trunk since about the time Leopard shipped. (way before it gets to
> actually running my code, it buserrors making a ruby subclass of
> NSObject. )
>
> Users are grumping at me, so I'm willing to dig into it, but since
> its not my code, I'd prefer to debug it at the source level.
> Presumably there's some magic incantation to get XCode to find the
> RubyCocoa source from where I've checked it out, but I don't know what
> it is.
>
> So what are the steps you have to do so that XCode can debug both
> your app and RubyCocoa?
>
> 1. Does it require me to build rubycocoa in any special way?
>
> 2. Do I have to tell XCode where to look for the source files after
> that? I notice that 0.13 tries to find them on Laurent's hard drive,
> which is why I think #1 might apply...
>
>
> Pierce
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Rubycocoa-talk mailing list
> Rubycocoa-talk@...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

So I've had a crashing bug in rubycocoa upon starting my app from
trunk since about the time Leopard shipped. (way before it gets to
actually running my code, it buserrors making a ruby subclass of
NSObject. )
Users are grumping at me, so I'm willing to dig into it, but since
its not my code, I'd prefer to debug it at the source level.
Presumably there's some magic incantation to get XCode to find the
RubyCocoa source from where I've checked it out, but I don't know what
it is.
So what are the steps you have to do so that XCode can debug both
your app and RubyCocoa?
1. Does it require me to build rubycocoa in any special way?
2. Do I have to tell XCode where to look for the source files after
that? I notice that 0.13 tries to find them on Laurent's hard drive,
which is why I think #1 might apply...
Pierce

Got this output in my console when making this call:
OSX::NSBundle.mainBundle.pathForImageResource("blankImage")
'blankImage' exists and this works 99% of the times I run the app.
I recently found a blog post about this LocalJumpError which might be
helpful in identifying the problem:
Work at the dining table: Ruby blocks
gotchas<http://blog.sidu.in/2007/11/ruby-blocks-gotchas.html&gt;
2007-11-29 12:48:06.249 Blogo[19415] WebKitEditor#awakeFromNib:
LocalJumpError: unexpected return
/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/oc_import.rb:617:in
`_kvc_behavior_method_added'
/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/oc_import.rb:647:in
`method_added'
/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/oc_wrapper.rb:50:in
`ocm_send'
/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/oc_wrapper.rb:50:in
`method_missing'
/Users/bjackson/working/blogo/trunk/Blogo.app/Contents/Resources/WebKitEditor.rb:36:in
`setImageViewDefaultImage'
/Users/bjackson/working/blogo/trunk/Blogo.app/Contents/Resources/WebKitEditor.rb:25:in
`awakeFromNib'
/Users/bjackson/working/blogo/trunk/Blogo.app/Contents/Resources/rb_main.rb:27:in
`NSApplicationMain'
/Users/bjackson/working/blogo/trunk/Blogo.app/Contents/Resources/rb_main.rb:27
/Users/bjackson/working/blogo/trunk/Blogo.app/Contents/Resources/SACrashReporter.rb:74:in
`run_app'
/Users/bjackson/working/blogo/trunk/Blogo.app/Contents/Resources/rb_main.rb:3
Let me know if anyone needs more information. Thanks!
Ben