Eloy Duran
eloy.****@gmail*****
Mon Aug 17 16:41:10 JST 2009
I think using the latest RubyCocoa version will fix this for you. But you can verify that easily. If the newest version does fix you're problem, then you will have to either have the user install it (/ Library) or bundle the framework inside your app bundle, which is the most common practice because of its unobtrusive nature. There's plenty of info on the interwebs on bundling frameworks with your apps, but here's a page on RubyCocoa specifically: http://rubycocoa.sourceforge.net/EmbedRubyCocoa HTH, Eloy On Aug 17, 2009, at 1:04 AM, Gideon King wrote: > We have a shipping app which links against the rubycocoa framework, > and on what seems to be pretty much a random basis, we get crashes > like this: > > 0 libSystem.B.dylib 0x94888e42 __kill + 10 > 1 libSystem.B.dylib 0x948fb23a raise + 26 > 2 libSystem.B.dylib 0x94907679 abort + 73 > 3 libruby.1.dylib 0x0039ab60 rb_exc_new + 0 > 4 libruby.1.dylib 0x0040163f rb_gc_mark_trap_list + > 440 > 5 libSystem.B.dylib 0x948872bb _sigtramp + 43 > 6 ??? 0xffffffff 0 + 4294967295 > 7 libruby.1.dylib 0x003a96f6 rb_need_block + 128 > 8 libruby.1.dylib 0x003a6e2f rb_eval_string_wrap + > 15784 > 9 libruby.1.dylib 0x003a7da7 rb_eval_string_wrap + > 19744 > 10 libruby.1.dylib 0x003a882d rb_respond_to + 236 > 11 libruby.1.dylib 0x003a8916 rb_funcall + 33 > 12 libruby.1.dylib 0x003bbc96 rb_hash_aref + 83 > 13 com.apple.rubycocoa 0x0037b7ee > eval_ruby_program_for_class + 286 > 14 com.apple.AppKit 0x911593b1 +[NSBundle(NSNibLoading) > loadNibNamed:owner:] + 155 > > As you can see, in this case, it was just as we were loading a nib > that had nothing to do with ruby. In other situations it happens while > printing or while doing some image manipulation - seems pretty much > random. For some people it appears to happen a lot, and for others it > may only happen once in a few months. > > I understand that Leopard ships with version 0.13.1 of the framework, > so my questions are: > > 1. Is there a workaround for this issue while using the installed > framework on Leopard? > 2. Does the latest version of the framework fix this problem? > 3. Does the version in Snow Leopard (0.13.2) fix this problem? > 4. Can I get my users to update to a version that fixes the problem? I > see that the normal install puts it in /Library, so presumably my app > would still see the default one in /System > 5. Should I be looking to link the latest version to my app directly? > I really didn't want to do an update to my app at this point, but we > have had so many reports of this, that we really need to fix it asap. > > Thanks for your help. > > Gideon > > _______________________________________________ > Rubycocoa-devel mailing list > Rubyc****@lists***** > http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel
