Bug #2786

Segfault when loading gem

Added by Ryan Bates almost 2 years ago. Updated 10 months ago.

[ruby-core:28322]
Status:Closed Start date:02/24/2010
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
ruby -v:ruby 1.9.2dev (2010-02-24 trunk 26744) [x86_64-darwin10.0.0]

Description

I am occasionally getting a segfault error when using cucumber 0.6.2 with latest ruby trunk (26744) in Mac OS X 10.6.1. It is happening about 25% of the time I run the cucumber command. Here's the full error:

http://gist.github.com/312461#file_cucumber_segfault

From that error it looks like it is happening when calling the "gem" method and RubyGems is trying to raise an error when it can't find the gem. This is the line in cucumber (ansicolor.rb).

  gem 'genki-ruby-terminfo'

I tried to duplicate this by executing that line in irb. I get a Gem::LoadError saying the gem doesn't exist but never a segfault there.

Sorry if this isn't the right place to post this ticket.

Related issues

related to ruby-trunk - Bug #2976: cucumberでSEGV Closed 03/18/2010
related to ruby-trunk - Bug #2330: Non systematic segmentation fault with autoload rubyspec Closed 11/04/2009
related to ruby-trunk - Bug #3132: …/nokogiri-1.4.1/ext/nokogiri/nokogiri.bundle: [BUG] Bus ... Closed 04/12/2010
duplicates ruby-trunk - Bug #2529: Segmentation Fault is occasionally occurred in rake with ... Closed 12/25/2009

History

Updated by Dan PIckett almost 2 years ago

I can confirm this behavior as well with cucumber 0.6.4 and ruby trunk (27310) on Darwin 10.3 (OS X 10.6.3)

Updated by Dan PIckett almost 2 years ago

here's the backtrace information: http://gist.github.com/363031

Updated by Yui NARUSE almost 2 years ago

  • Status changed from Open to Closed
This issue was solved with changeset r27393.
Kenta, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

Also available in: Atom PDF