[Rubycocoa-devel 1415] Re: RubyCocoa in Snow Leopard

Back to archive index

Gideon King gideo****@novam*****
Sat Sep 5 21:22:22 JST 2009


It appears I was a little to hasty in thinking that RubyCocoa was  
stable using version 1.0.0 of the framework - I am getting crash  
reports from customers like this:

Thread 0 Crashed:
0   libSystem.B.dylib             	0x961d6e42 __kill + 10
1   libSystem.B.dylib             	0x9624923a raise + 26
2   libSystem.B.dylib             	0x96255679 abort + 73
3   libruby.1.dylib               	0x00325b60 rb_exc_new + 0
4   libruby.1.dylib               	0x0038c683 rb_gc_mark_trap_list + 508
5   libSystem.B.dylib             	0x961d52bb _sigtramp + 43
6   ???                           	0xffffffff 0 + 4294967295
7   com.apple.CoreFoundation      	0x905ab4fd CFStringGetDoubleValue +  
29
8   ...print.v583a.pde.DuplexPrint	0x1d1b6a4b CBJ_SetDispValue 
(BJPDEDuplexContext*) + 181
9   ...print.v583a.pde.DuplexPrint	0x1d1b36b2  
CBJ_MarginPDEPluginFactory + 1416
10  ...print.v583a.pde.DuplexPrint	0x1d1b38a1  
CBJ_MarginPDEPluginFactory + 1911
11  ...int.framework.Print.Private	0x1dc12258 AskUserForFile + 9710
12  ...int.framework.Print.Private	0x1dc0701f 0x1dc01000 + 24607
13  ...int.framework.Print.Private	0x1dc07558 0x1dc01000 + 25944
...

The user had not done anything that invokes the RubyCocoa framework  
directly - they had just printed a document. So far, it appears that  
the other crashes we saw under previous versions of the framework may  
have been fixed, but this one wasn't. One thing that concerns me is  
that all the other frameworks I have linked to in the application have  
a + beside them in the crash log, but the RubyCocoa one doesn't - any  
ideas why this would be the case? Is the + purely dependent on whether  
it is com.apple or not?

   0x2d4000 -   0x2f3ff7  com.apple.rubycocoa 1.0.0 (1.0.0)  
<bff3daa7494b7e8f886ebc179eb0b323> /Volumes/NovaMind 4 Pro/NovaMind  
Pro.app/Contents/Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa

Has anyone else encountered this? Any suggested workarounds?


Regards

Gideon




More information about the Rubycocoa-devel mailing list
Back to archive index