MacVim built on OS X 10.9 Mavericks crashes in libruby.2.0.0.dylib

[GoogleCodeExporter]

I have cloned the git repo and built MacVim myself on OS X 10.9 with XCode 
5.0.1 command line tools installed. I used this configuration:

export CC=clang
./configure --with-features=huge --enable-rubyinterp --enable-pythoninterp 
--enable-perlinterp --enable-cscope

This builds fine, but crashes on launch (both GUI and command line) with the 
attached crash log. The problem seems to be with ruby2 which is now default 
ruby in OS X 10.9. 

Interestingly enough, version I built on OS X 10.8.5 continues to work and ruby 
works too (things like command-t plugin which rely on ruby continue to work in 
OS X 10.9). 

Original issue reported on code.google.com by veritas....@gmail.com on 23 Oct 2013 at 5:19

Attachments:

• Vim_2013-10-23-125900_Nebula.crash

[GoogleCodeExporter]

The reason MacVim compiled on OS X 10.8.5 works in 10.9 is because I did 
upgrade install of OS X 10.9 which kept Ruby 1.8 in addition to installing Ruby 
2.0.

However, when I compile MacVim on Mac OS X 10.9 is does use Ruby 2.0 as 
reported by otool:

$ otool -L Vim
Vim:
    /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 20.0.0)
    /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 157.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)
    /usr/local/lib/libncurses.5.dylib (compatibility version 5.0.0, current version 5.0.0)
    /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
    /System/Library/Perl/5.16/darwin-thread-multi-2level/CORE/libperl.dylib (compatibility version 5.16.0, current version 5.16.2)
    /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.5)
    /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/libruby.2.0.0.dylib (compatibility version 2.0.0, current version 2.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 855.11.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
    /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1265.0.0)
    /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1056.0.0)
    /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 59.0.0)
$

Original comment by veritas....@gmail.com on 23 Oct 2013 at 9:35

[GoogleCodeExporter]

Ok, so the crash is due to Command-T being compiled against Ruby 1.8. If the 
extension is recompiled to link against Ruby 2, the crash goes away, so this 
can be closed.

Original comment by veritas....@gmail.com on 24 Oct 2013 at 7:06

[GoogleCodeExporter]

Great that you figured it out and shared your experience.  Thanks.

Original comment by bjorn.winckler@gmail.com on 25 Oct 2013 at 3:04

• Changed state: WontFix