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

[MacRuby] #294: Experimental: EmbeddedMacRuby example crashes
by MacRuby 07 Oct '09

07 Oct '09

#294: Experimental: EmbeddedMacRuby example crashes ---------------------------------+------------------------------------------ Reporter: illenberger@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ Steps to reproduce: - Checkout and build r1999 of macrub-experimental - build the EmbeddedMacRuby example under SnowLeopard 10A394 - In the upcoming app window, press the evaluate button The app will crash with the following trace: (gdb) bt #0 rb_vm_run (fname=0x916b4d "(eval)", node=0x18b71e0, binding=0x0, inside_eval=true) at compiler.h:53 #1 0x0016f5f8 in rb_vm_run_under (klass=0, self=25358272, fname=0x916b4d "(eval)", node=0x18b71e0, binding=0x0, inside_eval=<value temporarily unavailable, due to optimizations>) at vm.cpp:4009 #2 0x00123340 in eval_string (self=25358272, klass=0, src=25915360, scope=4, file=0x916b4d "(eval)", line=1) at vm_eval.c:352 #3 0x00123736 in rb_eval_string (str=0x18b6b30 "(0..42).to_a") at vm_eval.c:445 #4 0x0018a25a in rb_rval_to_ocid [inlined] () at /Users/frank/macruby- experimental/include/ruby/ruby.h:34 #5 0x0018a25a in -[MacRuby evaluateString:] (self=0x18290a0, _cmd=0x91759685, expression=0x18663a0) at MacRuby.m:34 #6 0x00002d08 in -[MyController evaluate:] (self=0x186bfd0, _cmd=0x2ebc, sender=0x185f800) at /Users/frank/Desktop/EmbeddedMacRuby/MyController.m:30 #7 0x9767599d in -[NSApplication sendAction:to:from:] () #8 0x97674443 in -[NSControl sendAction:to:] () #9 0x97674346 in -[NSCell _sendActionFrom:] () #10 0x976735f9 in -[NSCell trackMouse:inRect:ofView:untilMouseUp:] () #11 0x97672e8a in -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] () #12 0x976723ab in -[NSControl mouseDown:] () #13 0x9766f860 in -[NSWindow sendEvent:] () #14 0x975ca68a in -[NSApplication sendEvent:] () #15 0x975be0ce in -[NSApplication run] () #16 0x975a916c in NSApplicationMain () #17 0x00002a40 in main (argc=1, argv=0xbffff7e8) -- Ticket URL: <http://www.macruby.org/trac/ticket/294> MacRuby <http://macruby.org/>

1 1

MacRuby tips
by Matt Aimonetti 06 Oct '09

06 Oct '09

Because Googling for MacRuby issues can still be quite challenging, I decided to start blogging about small things that might be useful to others. My first post is about embedding a custom font into your application and then use it on a text field or somewhere else: http://merbist.com/2009/10/06/macruby-tips-embed-a-custom-font/ Searching the Cocoa doc and converting the result into MacRuby isn't hard. However, I am sure that other developers will also try to embed a custom font into one of their apps, and if a result shows up right away when they google the problem, their experience will be much better. Anyway, I hope this series of tips will be helpful, and if you are learning Cocoa and have a blog, you might also want to share what you've learned/discovered. - Matt

4 8

BridgeSupport Question
by Jordan Breeding 06 Oct '09

06 Oct '09

I have a question about whether I am seeing a bug in BridgeSupport or not. I am running Mac OS X 10.6.1 and have a custom framework that has some categories for Foundation/Cocoa classes. The following are the problem I noticed when using gen_bridge_metadata: 1) I have to include Cocoa/Cocoa.h in the files, Foundation/ Foundation.h doesn't seem to work even though those are really the only classes I am dealing with. 2) This is the bigger one, gen_bridge_metadata isn't picking up all of the methods/messages from my header, here is one of the headers: ===== #import <Cocoa/Cocoa.h> @interface NSArray (JBBAdditions) #pragma mark Instance Methods - (NSArray *)jbb_dictionariesWithKey:(NSString *)keyName; - (id)jbb_firstObject; - (BOOL)jbb_isEmpty; @end ===== but here is the relevant section of the .bridgesupport file: ===== <class name='NSArray'> <method selector='jbb_isEmpty'> <retval type='B'/> </method> </class> ===== Any ideas as to why it is behaving this way? It is doing this for all of the classes I have defined categories on (only defining one method/ message). Thanks for any input, Jordan

2 4

MacRuby on iPhone
by Антон Журавскій 06 Oct '09

06 Oct '09

Hi all, I know most of you are 100% pissed off by this topic, but does anybody work on porting MacRuby to iPhone? What are main issues around that (if any)? And do we have a chance to be alive when it finally gets there? I'm personaly very excited by Ruby in general and MacRuby in particular, so would like to help if I can. Best, Anton

2 4

trunk status update
by Laurent Sansonetti 06 Oct '09

06 Oct '09

Another status update, covering about 2 weeks of development. Highlights: - Early backtracing support. - Much better AOT compilation. Parts of the standard library are now pre-compiled for testing. - Migrated to LLVM top of tree. - Dispatcher performance is now back to normal (we lost about 30% due to gcc not inlining code). - Many bug fixes. We are content-complete for a first beta release of MacRuby 0.5. We will release it very soon then continue converging until the final 0.5 release. Details: - Better GCD documentation - Implemented Symbol.all_symbols - Rewrote the file loader (file.c) fixing a few bugs - Added preliminary support for backtracing / symbolication - Make sure stdio objects are never finalized - Fixed more eval/Binding bugs - Fixed END{} block - Fixed a memory problem in the libyaml extension - Fixed rescues in rescues (most cases) - Fixed a 10.5-only bug in the new Array class - Fixed a bug of the parser when dealing with byte strings - AOT: now compiling part of the stdlib (notably irb and rubygems) - AOT: fixed bugs in the compilation of defined?, undef, rb_eStandardError, literal ranges - Fixed a bug in the compilation of `for' loops - Fixed many minor compilation bugs discovered by the LLVM module verifier - The arguments resolver is now able to deal with any number of arguments - Fixed minor String bugs - Added autorelease and dealloc to the list of handled ignored selectors - Fixed a bug when instance variables were not visible from within an iterator in method called through KVO - Fixed an infinite recursion trying to convert an NSPathStore2 to a string - Moved to LLVM r82747, enabled LLVM multithreaded mode - Fixed GC problems in the parser - Create all ruby scopes with external linkage, otherwise the AOT compiler won't generate frame info for them - Fixed a bug when open would crash when mode is numeric - Now using a gcc constructor to initialize .rbo files - Added Dispatch::Semaphore + fixed a few things - Make sure RoxorVM instances created lazily have a valid thread accessor - Fixed a random bug of Numeric#chr - macruby is now SIGINT interruptible (but no exception is raised, yet) - Fixed a few 32-bit only bugs - Fixed a GC bug in builtin global variable setters - Fixed a bug in Set#to_a - Fixed the BridgeSupport parser to properly handle one liner <method> elements - Fixed variadic functions/methods calls - Fixed a few bugs in Array#pack - Fixed a serious bug in the way we used to promote strings to byte strings - Fixed a few bugs in IO#ioctl and IO#fcntl - Now separately compiling the dispatcher and forcing function inlining - Fixed a bug in File.open when file permissions were not taken into account - Make sure ivar slot generation is disabled when compiling attr accessors - Fixed a bug in the way we AOT compile super method cache - Added an empty Ruby template file - Improved the MacRuby Application template: Embed MacRuby target and some unit testing mechanism are added Laurent

3 9

Super not passing init: through to NSObject correctly?
by Michael Shapiro 06 Oct '09

06 Oct '09

Hi all, I searched a few months of the list archives and trac, but wasn't able to find reference to this. Calling `super` inside of an overridden #init function where no ruby ancestors define #init causes a segmentation fault. If I'm not mistaken, shouldn't the init: message be passed to NSObject? --------------------------------------------------------- class HasInit def init super p 'HasInit' self end end class A < HasInit; end class B < A; end A.new p 'A' B.new p 'B' class HasNoInit; end class C < HasNoInit; end class D < C def init super self end end C.new p 'C' D.new p 'D' --------------------------------------------------------- You should see the segfault happen when trying to init D, but HasInit passes the message through to NSObject just fine, it seems. Tested with the 2009-10-05-1158 nightly. Thanks! --Mike

3 3

implement Enumerable::Enumerator
by Giampiero De Ciantis 06 Oct '09

06 Oct '09

I wanted to contribute to the project and I am not sure what I am seeing. I ran the following specs: ./mspec/bin/mspec ci -B ./spec/macruby.mspec ./spec/frozen/core/ enumerator and ./mspec/bin/mspec ci -B ./spec/macruby.mspec ./spec/frozen/core/ enumerable Both of these groups of specs pass. Does that mean that the TODO item is done or am I not running the right commands? Cheers, -Gp

3 3

implementation of symbols
by Linan Wang 06 Oct '09

06 Oct '09

Hi, I read a little bit source codes and found out that Symbol is implemented on top of NSString. My question is if it's a better choice to use SEL as the basis when objc is available? objc runtime takes care of the registration and management. I guess using NSString class is a decision with good reasons, could anybody please shine some lights on it? Thanks Best wishes Linan

2 2

HotCocoa on_notification Method with Snow Leopard
by Trevor Hills 05 Oct '09

05 Oct '09

I have a small MacRuby/HotCocoa application that uses the on_notification method described by Richard Kilmer in his post of Sept 19 2008 http://lists.macosforge.org/pipermail/macruby-devel/2008-September/000539.h… This application worked well under MacRuby 0.4 and Mac OS 10.5. It intercepts Spotify Growl messages to obtain track title and artist information to pass into an AppleScript Studio application I wrote. The MacRuby/HotCocoa app was provided by a friendly software developer, Peter MacRobert, for me since ASS did not have the appropriate inter-process message handling capability. I upgraded to Snow Leopard and discovered that the app crashed out with MacRuby 0.4. I succeeded in downloading and installing MacRuby 0.5 and now the app loads successfully with no error messages as before under Leopard. Unfortunately the on_notification code does not get triggered any longer. No error messages, just stubbornly refuses to respond when the Distributed Notifications Center gets the Spotify message. I am able to see that the message is there by firing up Growl which shows the message each time Spotify plays a track. I'm looking for guidance if anybody has any words of wisdom please? Has something changed under MacOS 10.6.1 to do with the Distributed Notifications Center or is it likely that my re-installation of MacRuby 0.5 is incorrect and I have to do something additional to get the on_notification method re-enabled? My googling efforts suggest that there are changes in inter-process security with Snow Leopard but I am unable to discover any security violation error messages. Regards Trevor Hills

2 1

[MacRuby] #362: Add Unit Testing and Embed MacRuby to Project Template
by MacRuby 05 Oct '09

05 Oct '09

#362: Add Unit Testing and Embed MacRuby to Project Template ---------------------------------+------------------------------------------ Reporter: dylan@… | Owner: lsansonetti@… Type: enhancement | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ I'm attaching a new version of the default project template. To test you can copy it to one of the template directories such as : ~/Library/Application Support/Developer/Shared/Xcode/Project Templates/Application/ Differences: - Embed MacRuby target is included by default to easy deployment for first time users - Tests directory has been added for tests - test_stub.rb has been added with a starting test::unit case - Unit Tests target has been added to run the tests - test_suite.rb has been added to load up all tests from the Tests directory. This can easily be made recursive using Dir.glob. -- Ticket URL: <http://www.macruby.org/trac/ticket/362> MacRuby <http://macruby.org/>

1 9