On Oct 11, 2010, at 12:56 , John Barnette wrote:
On Oct 11, 2010, at 11:54 AM, Ryan Davis wrote:
I haven't tried using isolate on macruby yet, but let me know if you have any issues.
The tests segfault on 0.7 right now, I have a note to look at this before the next Isolate release.
I'm poking at it... I'm not even getting a segfault, just hanging out spinning CPU and eating a TON of RAM. It never even gets to the first test for some reason.
Here is a sample:
1968 rary_reserve
1968 rb_yield
1968 rb_vm_yield_args
1968 MREP_4A9E42EFE9E24C529FBC1397F1146174
1968 0x103324011
1968 rb_vm_dispatch
1968 MREP_4A9E42EFE9E24C529FBC1397F1146174
1968 0x103324011
1968 rb_vm_dispatch
1968 rb_f_eval
1968 rb_vm_run_under
1968 rb_vm_run
1968 0x102da92d3
1968 rb_vm_prepare_block
1968 rb_vm_const_is_defined
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1968 rb_str_NSCoder_decode
1967 rb_str_NSCoder_decode
1679 rb_str_NSCoder_decode
1659 rb_str_NSCoder_decode
20 rb_str_NSCoder_decode
288 rb_str_NSCoder_decode
1 rb_str_NSCoder_decode
Is there an easy way to know what NSCoder#decode is getting pissy about?