From: FUJIMOTO H. <hi...@im...> - 2003-11-12 23:55:34
|
At Wed, 12 Nov 2003 11:33:35 +1100, Charles Miller wrote: > On 12/11/2003, at 10:49 AM, Kevin Bullock wrote: > > I just subscribed, so I don't know if this has been discussed further, > > but I've been attempting to get RubyCocoa working on Panther, using > > the included ruby installation (1.6.8, libruby and headers are > > included, unlike in Jaguar). Despite applying the patch > > (http://www.imasy.or.jp/~hisa/mac/rubycocoa/build.en.html#label:19), I > > still get a segfault during the configure process. Here's a > > transcript: > > I had the same problem. The weird thing was that the segfault always > occurred during processing of the _second_ file in post-config.rb, no > matter which order I told it to process the files in. > > Running in gdb, I found the following backtrace: the problem seemed to > be happening in the garbage collector somewhere. > > Program received signal EXC_BAD_ACCESS, Could not access memory. > 0x00019918 in rb_gc_mark () > (gdb) bt > #0 0x00019918 in rb_gc_mark () > #1 0x00019f7c in rb_gc_mark () > #2 0x0001973c in rb_source_filename () > #3 0x0001a86c in rb_gc () > #4 0x000194b8 in rb_newobj () > > When I edited post-config.rb and put a call to "GC.start" right > underneath "load 'tool/create-appkit-and-foundation.rb'", the config > worked. I'm going to apply this modification into cvs repository of rubycocoa. Thank you for useful info. -- FUJIMOTO Hisakuni |