November 2010 - MacRuby-devel - lists.macosforge.org

Exception backtraces in instance_eval
by Martijn Walraven 14 Nov '10

14 Nov '10

Hi, I'm trying to use RSpec (latest version, 2.1.0) with MacRuby, but there seems to be information missing from the exception backtraces which makes it difficult to see where exactly specs fail. Running a straightforward helloworld_spec.rb with a failing example for instance, shows a reference to the failing line (hello_world.greeting.should == "Hello World!") in MRI Ruby 1.9.2: Failures: 1) A new HelloWorld object should return the appropriate greeting Failure/Error: hello_world.greeting.should == "Hello World!" expected: "Hello World!", got: "Hello Earth!" (using ==) # ./Spec/helloworld_spec.rb:6:in `block (2 levels) in <top (required)>' In MacRuby (0.7.1) however, RSpec displays a 'Failure/Error: Unable to find matching line from backtrace' instead, which makes sense with no traces present referring to the actual spec: Failures: 1) A new HelloWorld object should return the appropriate greeting Failure/Error: Unable to find matching line from backtrace expected: "Hello World!", got: "Hello Earth!" (using ==) # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:41:in `block' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:39:in `block' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:75:in `block' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:74:in `with_pending_capture' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:32:in `run:' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/example_group.rb:260:in `block' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/example_group.rb:257:in `run_examples:' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/example_group.rb:222:in `run:' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/command_line.rb:26:in `block' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/command_line.rb:15:in `run:' # /usr/local/rvm/gems/macruby-0.7.1@test/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:10:in `block' ' Looking at the complete backtrace in MRI Ruby 1.9.2 shows there seems to be a lot of information missing from the MacRuby backtrace. Apart from missing information about the context of a block and other differences in descriptions, MacRuby doesn't seem to list any traces beyond the instance_eval. The RSpec source (example.rb) shows it indeed uses instance_eval to evaluate the example block. I checked the backtraces in the rescue clauses there, but they don't contain traces from any execution beyond the instance_eval call. Is loss of exception backtraces in instance_eval a known limitations of MacRuby? Are there any plans to improve backtraces? Failures: 1) A new HelloWorld object should return the appropriate greeting Failure/Error: hello_world.greeting.should == "Hello World!" expected: "Hello World!", got: "Hello Earth!" (using ==) # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-expectations-2.1.0/lib/rspec/expectations/fail_with.rb:29:in `fail_with' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-expectations-2.1.0/lib/rspec/matchers/operator_matcher.rb:48:in `fail_with_message' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-expectations-2.1.0/lib/rspec/matchers/operator_matcher.rb:70:in `__delegate_operator' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-expectations-2.1.0/lib/rspec/matchers/operator_matcher.rb:60:in `eval_match' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-expectations-2.1.0/lib/rspec/matchers/operator_matcher.rb:29:in `block in use_custom_matcher_or_delegate' # ./Spec/helloworld_spec.rb:6:in `block (2 levels) in <top (required)>' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:42:in `instance_eval' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:42:in `block (2 levels) in run' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:81:in `call' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:81:in `with_around_hooks' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:39:in `block in run' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:75:in `call' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:75:in `block in with_pending_capture' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:74:in `catch' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:74:in `with_pending_capture' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example.rb:38:in `run' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example_group.rb:261:in `block in run_examples' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example_group.rb:257:in `map' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example_group.rb:257:in `run_examples' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/example_group.rb:231:in `run' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/command_line.rb:27:in `block (2 levels) in run' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/command_line.rb:27:in `map' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/command_line.rb:27:in `block in run' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/reporter.rb:12:in `report' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/command_line.rb:24:in `run' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:55:in `run_in_process' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:46:in `run' # /usr/local/rvm/gems/ruby-1.9.2-p0@test/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:10:in `block in autorun' Just for completeness' sake, this is the code from example.rb that runs the example: begin unless pending with_pending_capture do with_around_hooks do begin run_before_each @example_group_instance.instance_eval(&@example_block) rescue Exception => e set_exception(e) ensure run_after_each end end end end rescue Exception => e set_exception(e) ensure @example_group_instance.example = nil assign_auto_description end Thanks, Martijn

2 4

Can I install gems without sudo?
by Zhi-Qiang Lei 11 Nov '10

11 Nov '10

Dear All, Can I install gems without sudo? I want them to be installed in .gems under my home folder. Thanks. bogon% macgem install -V data_mapper Fetching http://rubygems.org/latest_specs.4.8.gz OK Fetching http://rubygems.org/specs.4.8.gz OK Installing gem extlib-0.9.15 unknown: warning: ignoring alias unknown: warning: ignoring alias ERROR: While executing gem ... (Errno::EACCES) Permission denied - /Library/Frameworks/MacRuby.framework/Versions/0.7/usr/lib/ruby/Gems Best regards, Zhi-Qiang Lei zhiqiang.lei(a)gmail.com

3 3

sharedRuntime same context as MacRuby's runtime
by Louis-Philippe 11 Nov '10

11 Nov '10

Hi, I am trying to implement some macruby pre-initialisation inside an Objective-C class, to enhance the Objective-C class with some ruby methods before returning the initialized object to MacRuby. I was wondering if the + MacRuby sharedRuntime execution context is the same as my MacRuby application execution context? Right now, it does not seem like the sharedRuntime preparation I do inside my Objective-C initializer does affect my MacRuby execution: in MacRuby: framework "MyObjCFramework" myObject = MyClass.enhancedInitializer in Objective-C: // MyObjCFramework ... + (id)enhancedInitializer { id myInstance = [MyClass regularInitializer]; NSBundle * fbundle = [NSBundle bundleForClass:[MyClass class]]; NSString * rbPath = [fbundle pathForResource:@"myClass_ruby" ofType:@"rb"]; [[MacRuby sharedRuntime] evaluateFileAtPath:rbPath]; return myInstance; } Is something like this supposed to be possible? Thanks! L-P

6 11

Compiled Ruby files
by Larry Wilson 09 Nov '10

09 Nov '10

I've been poking around in the directories of a MacRuby-based app (that has been compiled via macruby-deploy) in the usr/lib/ruby subdirectories. Why is there not an .rbo file for every .rb source file? Is it safe to delete the .rb files if there is a .rbo equivalent? -Larry

3 5

System crash - MacRuby priority
by Robert Rice 07 Nov '10

07 Nov '10

I determined that my system crash was not due to an endless loop - rather due to a very inefficient algorithm. MacRuby seems to run at such a high priority that it can cause the system to crash - especially if a streaming video is running. Can I lower the priority of my MacRuby application? Thanks, Bob Rice

5 6

macgem and previously installed gems
by Andy Park 07 Nov '10

07 Nov '10

I'm trying to get macirb that came with my new MacRuby installation to play nice ly with the existing .irbrc, where I'm using a lot of gems previously installed with gem. It looks like my gems aren't found by macirb because they were install ed with gem, so are not found / used by macgem. Would I really need to install a ll my gems using macgem in order to work with macirb using my existing .irbrc?

2 1

Creating a pdf : Cocoa to MacRuby translation
by Julien Jassaud 07 Nov '10

07 Nov '10

Hello to every one, I am trying to programmatically create a pdf. I have this quite simple code in Cocoa that works perfectly : #import <Cocoa/Cocoa.h> #import <Foundation/Foundation.h> int main (int argc, const char * argv[]) { NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init]; CGContextRef pdfContext; CFStringRef path; CFURLRef url; CGRect pageRect; path = CFStringCreateWithCString(NULL, "./my_pdf.pdf", kCFStringEncodingUTF8); url = CFURLCreateWithFileSystemPath(NULL, path, kCFURLPOSIXPathStyle, 0); CFRelease (path); pageRect = NSMakeRect(0,0,100,100); pdfContext = CGPDFContextCreateWithURL(url, &pageRect, nil); CFRelease(url); CGPDFContextBeginPage(pdfContext, nil); CGContextSetCMYKFillColor(pdfContext, 1.0, 0.0, 0.0, 0.0, 1.0); CGContextFillRect(pdfContext, NSMakeRect(30, 30, 40, 40)); CGPDFContextEndPage(pdfContext); CGPDFContextClose(pdfContext); [pool drain]; return 0; } After running this program I get a pdf in perfect working order. I tried to port this little example to MacRuby like so : framework 'Cocoa' url = CFURLCreateWithFileSystemPath(nil, './my_pfd.pdf', KCFURLPOSIXPathStyle, 0) page_rectangle = NSMakeRect(0,0,100,100) page_rectangle_pointer = Pointer.new_with_type('{CGRect={CGPoint=dd}{CGSize=dd}}') pdf_context = CGPDFContextCreateWithURL(url, page_rectangle_pointer, nil) CGPDFContextBeginPage(pdf_context, nil) CGContextSetCMYKFillColor(pdf_context, 1.0, 0.0, 0.0, 0.0, 1.0) CGContextFillRect(pdf_context, NSMakeRect(30, 30, 40, 40)) CGPDFContextEndPage(pdf_context) CGPDFContextClose(pdf_context) This do produces a pdf but it is completely empty. Also, MacRuby complains when called with the -w option : $ macruby -w cocoapdf.rb unknown: warning: instance variable __octype__ not initialized Does anybody have an idea what I am doing wrong ? Thanks, Julien Jassaud

5 7

installation help
by Mikie Atsukawa 06 Nov '10

06 Nov '10

Hi, I'm trying to install MacRuby for the first time and I have followed procedures in README.rdoc up until "rake" When entering rake, I encountered this error (output of second time running rake): ** Invoke default (first_time) ** Invoke all (first_time) ** Invoke macruby (first_time) ** Invoke macruby:build (first_time) ** Invoke macruby:dylib (first_time) ** Invoke rbconfig (first_time) ** Invoke miniruby (first_time) ** Invoke files (first_time) ** Invoke config_h (first_time) ** Execute config_h ** Invoke dtrace_h (first_time) ** Execute dtrace_h ** Invoke revision_h (first_time) ** Execute revision_h ** Invoke mark_gc (first_time) ** Execute mark_gc ** Execute files ** Execute miniruby ** Execute rbconfig ** Invoke files ** Execute macruby:dylib ** Invoke macruby:static (first_time) ** Invoke files ** Execute macruby:static ** Execute macruby:build ** Execute macruby ** Invoke stdlib:build (first_time) ** Invoke miniruby ** Invoke macruby:dylib ** Execute stdlib:build ./miniruby -I. -I./lib bin/rubyc --internal --arch i386 --arch x86_64 -C "rbconfig.rb" -o "./rbconfig.rbo" Assertion failed: (Kind == NewKind && "FIXME: Unable to handle custom metadata mismatch!"), function ParseMetadata, file BitcodeReader.cpp, line 865. rake aborted! Command failed with status (): [./miniruby -I. -I./lib bin/rubyc --interna...] /Users/mikie/.rvm/gems/ruby-1.9.2-p0/gems/rake-0.8.7/lib/rake.rb:995:in `block in sh' /Users/mikie/.rvm/gems/ruby-1.9.2-p0/gems/rake-0.8.7/lib/rake.rb:1010:in `call' /Users/mikie/.rvm/gems/ruby-1.9.2-p0/gems/rake-0.8.7/lib/rake.rb:1010:in `sh' /Users/mikie/.rvm/gems/ruby-1.9.2-p0/gems/rake-0.8.7/lib/rake.rb:1094:in `sh' /Users/mikie/Downloads/MacRuby/rakelib/builder/builder.rb:21:in `block (3 levels) in parallel_execute' /Users/mikie/Downloads/MacRuby/rakelib/builder/builder.rb:21:in `each' /Users/mikie/Downloads/MacRuby/rakelib/builder/builder.rb:21:in `block (2 levels) in parallel_execute' Any help is appreciated, thank you.

3 2

IRB update
by Eloy Duran 05 Nov '10

05 Nov '10

Hi, As some of you may know, we have a new implementation of IRB since MacRuby 0.7. My hope was nobody would notice the changes, but this was obviously wishful thinking :) So from now on, whenever there are major changes, I’ll write an update about them. I’d be very grateful if people can try MacRuby trunk or the nightly installer package. Alternatively, you should be able to install the gem version (on MRI 1.9 as well), although I haven't tried this myself: https://rubygems.org/gems/dietrb Last night I’ve updated the included version to 0.6.0. This version adds the following features: * Auto-indentation, which is enabled by default. * Complete file paths in strings. This works for strings that have *not* been closed yet. Cheers, Eloy

1 0

MacRuby methods with external frameworks
by Louis-Philippe 04 Nov '10

04 Nov '10

Hi all, I have a funny problem, I have a framework I created, ObjCHiredis <http://github.com/lp/ObjCHiredis>, which works with MacRuby. Except I can't use methods with more than one arguments in it??? like: ObjCHiredis.redis works fine but ObjCHiredis.redis("127.0.0.1", on:6379) doesn't. ??? I know from my methods are OK as my Framework test suite, in Objective-C passes the test, and I tried it in an other Objective-C runtime language, Nu, which handles it flawlessly. I first thought this problem was related to methods arguments overload, but an other very unique method also does it: framework "ObjCHiredis" p redis = ObjCHiredis.alloc.init p redis.connect("127.0.0.1", on:6379) => #<ObjCHiredis:0x2000d5c80> => wrong number of arguments (2 for 0) (ArgumentError) I feel like the error must be mine... but it works elsewhere and I looked everywhere for a solution inside my code without avail. thanks! L-P

4 11