Re: [MacRuby-devel] [ANN] MacRuby 0.7
On 06/10/2010, at 1:00 AM, macruby-devel-request@lists.macosforge.org wrote:
After 5 months of development since the last release, MacRuby 0.7 is now available. Get it here while it's still hot!
cool! Now that 0.7 is out I've just tried to "macgem install control_tower", but it's warning me that it'll stomp (at least) on the existing /usr/bin/rackup from my OSX standard ruby 1.8.7 install. I guess this is more a RubyGems question, but is there an easy way to specify a different install directory for gem executables? cheers Russell
On 06/10/2010, at 3:08 PM, russell muetzelfeldt wrote:
On 06/10/2010, at 1:00 AM, macruby-devel-request@lists.macosforge.org wrote:
After 5 months of development since the last release, MacRuby 0.7 is now available. Get it here while it's still hot!
cool!
Now that 0.7 is out I've just tried to "macgem install control_tower", but it's warning me that it'll stomp (at least) on the existing /usr/bin/rackup from my OSX standard ruby 1.8.7 install. I guess this is more a RubyGems question, but is there an easy way to specify a different install directory for gem executables?
http://rvm.beginrescueend.com/ ? or use bundler from rails (which IIUC is independent of rails) Antony Blakey ------------- CTO, Linkuistics Pty Ltd Ph: 0438 840 787 It is no measure of health to be well adjusted to a profoundly sick society. -- Jiddu Krishnamurti
On Oct 5, 2010, at 22:40 , Antony Blakey wrote:
http://rvm.beginrescueend.com/ ? or use bundler from rails (which IIUC is independent of rails)
or isolate, the smaller cleaner happier alternative to bundler. I haven't tried using isolate on macruby yet, but let me know if you have any issues.
+1 for Isolate, I use it every day at work Sent from my iPhone On Oct 11, 2010, at 12:56, John Barnette <jbarnette@gmail.com> 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.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
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?
Hi Ryan, On Oct 12, 2010, at 2:52 PM, Ryan Davis wrote:
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?
Hard to tell, how do you reproduce this? I wouldn't look too much at the stacktrace, since the symbols might be corrupted. Laurent
participants (6)
-
Antony Blakey
-
John Barnette
-
Laurent Sansonetti
-
Matt Aimonetti
-
russell muetzelfeldt
-
Ryan Davis