Bug #5973: Bus Error in simple project requiring YARD

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin11.0.1]

[ggilder (Gabriel Gilder)]

Hi, I've created a simple sample project that reliably triggers a bus error in Ruby 1.9.2p290 on Mac OS X. It seems to be triggered simply by requiring the YARD gem.

I've posted the sample project to reproduce the error here:
https://github.com/ggilder/ruby_segfault_test

And I've attached the error message generated, and the CrashReporter log.

Thanks,
-Gabriel

[ggilder (Gabriel Gilder)]

• File ruby-1.9.2-p290.log ruby-1.9.2-p290.log added

Error message attached

[naruse (Yui NARUSE)]

How did you install the ruby-1.9.2?
You built it with clang, didn't it?

[naruse (Yui NARUSE)]

• Status changed from Open to Feedback

Could you try build ruby-1.9.2 with gcc-4.2, or build ruby-1.9.3-head (p26 or later),
and run the test with it?

[ggilder (Gabriel Gilder)]

Sorry for the delay, I did not receive any email notification of an update on this thread.

I've just tried with ruby 1.9.3p0 and it does work fine. However, I did see the same issue with 1.9.3 in a larger project... sorry, I know that's not really enough to go on.

I believe you are probably correct that my ruby versions are built with clang — I am building them with RVM on Mac OS X Lion, so I think clang/LLVM is the default.

Are there known issues building ruby with LLVM/clang?

[naruse (Yui NARUSE)]

Gabriel Gilder wrote:

Sorry for the delay, I did not receive any email notification of an update on this thread.

I've just tried with ruby 1.9.3p0 and it does work fine. However, I did see the same issue with 1.9.3 in a larger project... sorry, I know that's not really enough to go on.

I believe you are probably correct that my ruby versions are built with clang — I am building them with RVM on Mac OS X Lion, so I think clang/LLVM is the default.

Are there known issues building ruby with LLVM/clang?

As I wrote in [ruby-core:42390], ruby 1.9.3-p26 fixes some bugs around LLVM/clang's optimization.
So your issue should be fixed until it is derived from known LLVM/clang bugs.
Please try 1.9.3-p125.

[ggilder (Gabriel Gilder)]

Thanks, I tried with 1.9.3-p125 and the problem does seem to be resolved.

[naruse (Yui NARUSE)]

• Status changed from Feedback to Closed