September 2009 - MacRuby-devel - lists.macosforge.org

[MacRuby] #305: boilerplate hotcocoa project crashes
by MacRuby 04 Sep '09

04 Sep '09

#305: boilerplate hotcocoa project crashes --------------------------------+------------------------------------------- Reporter: crafterm@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: hotcocoa crash --------------------------------+------------------------------------------- Hi There, Hope all is going well. When creating a boilerplate hotcocoa project, running macrake builds the project and creates the resultant foo.app file, however this .app file crashes and fails to start. Taking the generated application.rb file into macirb and attempting to run it manually results in the following error: irb(main):043:0> Application.new.start NameError: uninitialized constant LayoutView from 0:in `const_missing:' from 0:in `const_missing:' from 0:in `init_with_options:' from 0:in `window:' from 0:in `handle_block:' from 0:in `application:' from 0:in `start' from 0:in `eval:' from 0:in `evaluate:' from 0:in `evaluate:' from 0:in `signal_status:' from 0:in `class_eval:' from 0:in `each_top_level_statement' from 0:in `eval_input' from 0:in `start:' Any thoughts how to remedy? Cheers, Marcus -- Ticket URL: <http://www.macruby.org/trac/ticket/305> MacRuby <http://macruby.org/>

2 8

nightly build 2009-09-04
by Matt Aimonetti 04 Sep '09

04 Sep '09

http://dl.getdropbox.com/u/163257/macruby_nightly-2009-09-04.pkg in this build: new improved IO, socket(incomplete) and bug fixes Enjoy, - Matt

1 0

[MacRuby] #321: macgem crashes with "unknown: [BUG] Segmentation fault".
by MacRuby 04 Sep '09

04 Sep '09

#321: macgem crashes with "unknown: [BUG] Segmentation fault". ---------------------------+------------------------------------------------ Reporter: occam@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: ---------------------------+------------------------------------------------ macgem crashes with "unknown: [BUG] Segmentation fault". I tracked it to rubygems/config_file.rb:118): operating_system_config = Marshal.load Marshal.dump(OPERATING_SYSTEM_DEFAULTS) which crashes in the Marshal.load. Assuming the Marshal.dump is working (I can't confirm), the crash leads to macruby/marshal.c:1037ff where "RSTRING_LEN(arg->src)" blows up in a conditional: if (RSTRING_LEN(arg->src) > arg->offset) { The RSTRING_LEN macro tracks to CFStringGetLength crashing on "ptr" at macruby/string.c:625ff: long rb_str_clen(VALUE ptr) { return CFStringGetLength((CFStringRef)ptr); } The "VALUE ptr" gets passed in from Marshal.load and blows up in CFStringGetLength. I'm not sure whether the parameter is broken (though it seems valid), or whether perhaps Snow Leopard changed CFStringRef so that MacRuby's "struct load_arg *" needs to be updated to maintain compatibility. With luck, this issue is not too hard for a more astute debugger (or somone with knowledge of SL's CFStringRef) to solve. It would be nice to have macgem working (not to mention Marshal'ing). -- Ticket URL: <http://www.macruby.org/trac/ticket/321> MacRuby <http://macruby.org/>

1 5

Help Debugging MacRuby
by Jordan Breeding 03 Sep '09

03 Sep '09

I am on trunk, I am trying to create a reproducible, small test case for a failure I see in one of my programs when running it on MacRuby instead of 1.8 or 1.9. What are the commands to issue in gdb to see everything from every thread?

2 1

[MacRuby] #324: improve bench.rb
by MacRuby 03 Sep '09

03 Sep '09

#324: improve bench.rb -------------------------------------+-------------------------------------- Reporter: jordan.breeding@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- Currently bench.rb has a few inconsistencies (number printed to screen is not the number of times looped) and doesn't work well under ruby 1.8 or 1.9. Having it work on multiple versons of ruby is useful for benchmarking regressions against other ruby versions. I am including a patch I use locally to use able to run bench.rb under all ruby versions (by catching errors). {{{ diff --git a/bench.rb b/bench.rb index e05833b..2c47c62 100644 --- a/bench.rb +++ b/bench.rb @@ -7,6 +7,16 @@ # The same script can also be executed using /usr/bin/ruby or ruby19 to # compare the implementations. +def executeWithErrorHandling + if (block_given?) + begin + yield + rescue Exception => e + print(" ************* BENCHMARK FAILED ************* ") + end + end +end + def fib(n) if n < 3 1 @@ -80,168 +90,248 @@ Benchmark.bm(30) do |bm| # Fixnum arithmetic. bm.report('10 fib(30)') do - i=0; while i<10; fib(30); i+=1; end + executeWithErrorHandling do + i=0; while i<10; fib(30); i+=1; end + end end bm.report('10 fib(35)') do - i=0; while i<10; fib(35); i+=1; end + executeWithErrorHandling do + i=0; while i<10; fib(35); i+=1; end + end + end + bm.report('tak') do + executeWithErrorHandling do + tak(18,9,0) + end + end + bm.report('tarai') do + executeWithErrorHandling do + tarai(12,6,0) + end end - bm.report('tak') { tak(18,9,0) } - bm.report('tarai') { tarai(12,6,0) } - if RUBY_VERSION.to_f > 1.8 - # Ruby 1.8 is too weak for this benchmark. - bm.report('ackermann') { ack(3,9) } + bm.report('ackermann') do + executeWithErrorHandling do + ack(3,9) + end end # Loops. bm.report('10000000 times loop') do - 3000000.times {} + executeWithErrorHandling do + 10000000.times {} + end end bm.report('30000000 times loop') do - 30000000.times {} + executeWithErrorHandling do + 30000000.times {} + end end bm.report('10000000 while loop') do - i=0; while i<10000000; i+=1; end + executeWithErrorHandling do + i=0; while i<10000000; i+=1; end + end end bm.report('60000000 while loop') do - i=0; while i<60000000; i+=1; end + executeWithErrorHandling do + i=0; while i<60000000; i+=1; end + end end # Messages. bm.report('30000000 msg w/ 0 arg') do - o = Class1.new - i=0; while i<10000000; o.method1; o.method1; o.method1; i+=1; end + executeWithErrorHandling do + o = Class1.new + i=0; while i<30000000; o.method1; o.method1; o.method1; i+=1; end + end end bm.report('30000000 msg w/ 1 arg') do - o = Class1.new - i=0; while i<10000000; o.method2(i); o.method2(i); o.method2(i); i+=1; end + executeWithErrorHandling do + o = Class1.new + i=0; while i<30000000; o.method2(i); o.method2(i); o.method2(i); i+=1; end + end end bm.report('10000000 super w/ 0 arg') do - o = Class2.new - i=0; while i<10000000; o.method1; i+=1; end + executeWithErrorHandling do + o = Class2.new + i=0; while i<10000000; o.method1; i+=1; end + end end bm.report('10000000 super w/ 1 arg') do - o = Class2.new - i=0; while i<10000000; o.method2(i); i+=1; end + executeWithErrorHandling do + o = Class2.new + i=0; while i<10000000; o.method2(i); i+=1; end + end end bm.report('10000000 #send') do - o = Class1.new - i=0; while i<10000000; o.send(:method1); i+=1; end + executeWithErrorHandling do + o = Class1.new + i=0; while i<10000000; o.send(:method1); i+=1; end + end end bm.report('30000000 tail calls') do - tail(30000000) + executeWithErrorHandling do + tail(30000000) + end end # Instance variables. - bm.report('10000000 ivar read') { bench_ivar_read(10000000) } - bm.report('30000000 ivar read') { bench_ivar_read(30000000) } - bm.report('10000000 ivar write') { bench_ivar_write(10000000) } - bm.report('30000000 ivar write') { bench_ivar_write(30000000) } + bm.report('10000000 ivar read') do + executeWithErrorHandling do + bench_ivar_read(10000000) + end + end + bm.report('30000000 ivar read') do + executeWithErrorHandling do + bench_ivar_read(30000000) + end + end + bm.report('10000000 ivar write') do + executeWithErrorHandling do + bench_ivar_write(10000000) + end + end + bm.report('30000000 ivar write') do + executeWithErrorHandling do + bench_ivar_write(30000000) + end + end # Const lookup. bm.report('30000000 const') do - i=0; while i<30000000; i+=ConstantOne; end + executeWithErrorHandling do + i=0; while i<30000000; i+=ConstantOne; end + end end # Blocks bm.report('30000000 yield') do - o = Class1.new - o.yield1(30000000) {} + executeWithErrorHandling do + o = Class1.new + o.yield1(30000000) {} + end end bm.report('30000000 msg w/ block+yield') do - o = Class1.new - i=0; while i<30000000; o.yield2 {}; i+=1; end + executeWithErrorHandling do + o = Class1.new + i=0; while i<30000000; o.yield2 {}; i+=1; end + end end bm.report('30000000 Proc#call') do - o = proc {} - i=0; while i<30000000; o.call; i+=1; end + executeWithErrorHandling do + o = proc {} + i=0; while i<30000000; o.call; i+=1; end + end end bm.report('30000000 dvar write') do - i=0 - 30000000.times { i=1 } + executeWithErrorHandling do + i=0 + 30000000.times { i=1 } + end end # Eval bm.report('1000 eval') do - i=0 - s = "#{1+1}+#{20+20}" - while i<1000 - eval(s) - i+=1 + executeWithErrorHandling do + i=0 + s = "#{1+1}+#{20+20}" + while i<1000 + eval(s) + i+=1 + end end end bm.report('30000000 binding-var write') do - i=0 - eval('while i<30000000; i+=1; end') + executeWithErrorHandling do + i=0 + eval('while i<30000000; i+=1; end') + end end # Break bm.report('30000000 while break') do - i=0; while i<30000000; while true; i+=1; break; end; end + executeWithErrorHandling do + i=0; while i<30000000; while true; i+=1; break; end; end + end end bm.report('10000000 block break') do - i=0; while i<10000000; 1.times { i+=1; break }; end + executeWithErrorHandling do + i=0; while i<10000000; 1.times { i+=1; break }; end + end end # Next bm.report('30000000 while next') do - i=0; while i<30000000; i+=1; next; exit; end + executeWithErrorHandling do + i=0; while i<30000000; i+=1; next; exit; end + end end bm.report('10000000 block next') do - i=0; while i<10000000; 1.times { i+=1; next; exit; }; end + executeWithErrorHandling do + i=0; while i<10000000; 1.times { i+=1; next; exit; }; end + end end # Exception handlers. bm.report('60000000 begin w/o exception') do - i=0 - while i<60000000 - begin - i+=1 - rescue + executeWithErrorHandling do + i=0 + while i<60000000 + begin + i+=1 + rescue + end end end end bm.report('60000000 ensure w/o exception') do - i=0 - while i<60000000 - begin + executeWithErrorHandling do + i=0 + while i<60000000 begin + begin + ensure + i+=1 + end ensure i+=1 end - ensure - i+=1 end end end bm.report('50000 raise') do - i=0 - while i<50000 - begin - raise - rescue - i+=1 + executeWithErrorHandling do + i=0 + while i<50000 + begin + raise + rescue + i+=1 + end end end end # Method bm.report('3000000 Method#call w/ 0 arg') do - o = Class1.new - m = o.method(:method1) - i=0 - while i<3000000 - m.call - i+=1 + executeWithErrorHandling do + o = Class1.new + m = o.method(:method1) + i=0 + while i<3000000 + m.call + i+=1 + end end end bm.report('3000000 Method#call w/ 1 arg') do - o = Class1.new - m = o.method(:method2) - i=0 - while i<3000000 - m.call(i) - i+=1 + executeWithErrorHandling do + o = Class1.new + m = o.method(:method2) + i=0 + while i<3000000 + m.call(i) + i+=1 + end end end - end }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/324> MacRuby <http://macruby.org/>

1 4

[MacRuby] #325: replace "uncatched" with "uncaught"
by MacRuby 03 Sep '09

03 Sep '09

#325: replace "uncatched" with "uncaught" -------------------------------------+-------------------------------------- Reporter: jordan.breeding@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- the word "uncatched" sounds odd, "uncaught" is more commonly used, switch to it {{{ diff --git a/vm.cpp b/vm.cpp index 281d12d..79b1712 100644 --- a/vm.cpp +++ b/vm.cpp @@ -4538,7 +4538,7 @@ rb_vm_print_current_exception(void) { VALUE exc = GET_VM()->current_exception(); if (exc == Qnil) { - printf("uncatched Objective-C/C++ exception...\n"); + printf("uncaught Objective-C/C++ exception...\n"); std::terminate(); } }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/325> MacRuby <http://macruby.org/>

1 1

[MacRuby] #322: Instance variable memory layout error
by MacRuby 03 Sep '09

03 Sep '09

#322: Instance variable memory layout error ------------------------+--------------------------------------------------- Reporter: dev@… | Owner: lsansonetti@… Type: defect | Status: new Priority: critical | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: ------------------------+--------------------------------------------------- {{{ macruby -e "class C; def m; @v1 = @v2 = @v3 = @v4 = @v5 = @v6 = @v7 = @v8 = @v9 = @v10 = 0; end; def test; p @oops; end; end; c = C.new.test" }}} gives a false instead of nil! If I use less than 10 variables everything is fine, so I suppose that this is a (serious) memory layout problem! I am on OS 10.5.7 with MacRuby r2454. -- Ticket URL: <http://www.macruby.org/trac/ticket/322> MacRuby <http://macruby.org/>

1 3

HotCocoa, Snow Leopard and MacRuby trunk
by Dave Baldwin 03 Sep '09

03 Sep '09

I have just upgraded to Snow Leopard and found MacRuby 0.4 didn't work. Upgraded to the latest trunk using the instructions found here: http://redartisan.com/2009/9/1/macruby-intro Having done this I cannot run some of the HotCocoa examples. For calculato, layout_view and hotconsole doing a macrake just hangs. Doing a macrake -- trace did get the examples to build and run. Subsequent macrake then launched the example and they appear to work, however macrake never exits even when the app is quit. Doing a macrake clean (also never ends) will replicate the above behaviour. The "demo" example exhibits similar behaviour but the window is displayed and then unexpectedly quits. Are these known problems or is there a problem with my build of MacRuby? MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64] Thanks, Dave.

2 3

Upgrading Your Rails Development Environment for Snow Leopard
by Case 03 Sep '09

03 Sep '09

Now that Snow Leopard is out, thousands of devoted Mac/Ruby developers are jumping on the upgrade bandwagon. This guide should help get your Rails dev environment back up and running by upgrading key libraries to the new 64-bit computing system. http://www.metaspring.com/blog/development/ruby/upgrading-your-rails-develo… Case Ernsting Ann Arbor, MI

1 0

nightly build test
by Matt Aimonetti 03 Sep '09

03 Sep '09

Here is a nightly build fresh from my oven: http://dl.getdropbox.com/u/163257/macruby_nightly-2009-09-03.pkg It's SL only but if you don't feel like installing LLVM etc.. you might want to give it a try. Let me know if you encounter any issues, hopefully the project will be able to offer "official" nightly builds pretty soon. (otherwise, I might just run the script on my mac mini and sync with dropbox :p) - Matt p.s: Sorry Mike, I didn't forget you, I promise I'll look at your tutorial ASAP :(

1 0