# SystemStackError with gem installs, 1.8.7-p248 **URL:** \ **Category:** Ruby\ **Created:** [December 30, 2009, 2:41pm UTC](https://www.ruby-forum.com/t/systemstackerror-with-gem-installs-1-8-7-p248/180857 "2009-12-30T14:41:28Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [December 30, 2009, 2:41pm UTC](https://www.ruby-forum.com/t/systemstackerror-with-gem-installs-1-8-7-p248/180857/1 "2009-12-30T14:41:28Z")
Hi, I upgraded to ruby 1.8.7 p248 yesterday. Since then I’ve started seeing these error messages on gem installs: dberger@globe-madison ~\>sudo gem install sys-filesystem Password: Building native extensions. This could take a while… Successfully installed sys-filesystem-0.3.2 1 gem installed ERROR: While executing gem … (SystemStackError) stack level too deep The gem appears to install fine. It’s just that final error message that’s started showing up. I saw the same thing with passenger. Here’s my environment: dberger@globe-madison ~\>gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.7 (2009-12-24 patchlevel 248) [i686- darwin10.2.0] - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.8 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /usr/local/bin - RUBYGEMS PLATFORMS: - ruby - x86-darwin-10 - GEM PATHS: - /usr/local/lib/ruby/gems/1.8 - /Users/dberger/.gem/ruby/1.8 - GEM CONFIGURATION: - :update\_sources =\> true - :verbose =\> true - :benchmark =\> false - :backtrace =\> false - :bulk\_threshold =\> 1000 - “gemcutter\_key” =\> “330e8dd81e58e5b50e5a28fe920ec166” - :sources =\> [“[http://gemcutter.org](http://gemcutter.org)”, “http:// [gems.rubyforge.org/](http://gems.rubyforge.org/)”, “[http://gems.github.com](http://gems.github.com)”] - REMOTE SOURCES: - [http://gemcutter.org](http://gemcutter.org) - [http://gems.rubyforge.org/](http://gems.rubyforge.org/) - [http://gems.github.com](http://gems.github.com) Anyone else seeing this? BTW, running with --verbose provided no additional clues for me. Regards, Dan ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [December 31, 2009, 1:55am UTC](https://www.ruby-forum.com/t/systemstackerror-with-gem-installs-1-8-7-p248/180857/2 "2009-12-31T01:55:16Z")
On Wed, Dec 30, 2009 at 10:41:06PM +0900, Daniel B. wrote: > ERROR: While executing gem … (SystemStackError) > stack level too deep > > The gem appears to install fine. It’s just that final error message > that’s started showing up. I saw the same thing with passenger. Here’s > my environment: Maybe it’s happening when the RDoc gets generated? What version of RDoc do you have installed? ---
**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\ **Post date:** [December 31, 2009, 4:41pm UTC](https://www.ruby-forum.com/t/systemstackerror-with-gem-installs-1-8-7-p248/180857/3 "2009-12-31T16:41:19Z")
On Dec 30, 5:53 pm, Aaron P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > 1 gem installed > > ERROR: While executing gem … (SystemStackError) > > stack level too deep > > > The gem appears to install fine. It’s just that final error message > > that’s started showing up. I saw the same thing with passenger. Here’s > > my environment: > > Maybe it’s happening when the RDoc gets generated? What version of RDoc > do you have installed? Ah, I discovered the problem once I remembered the ‘–debug’ option. Turns out it’s an issue with yard: ERROR: While executing gem … (SystemStackError) stack level too deep /usr/local/lib/ruby/gems/1.8/gems/yard-0.5.2/lib/rubygems\_plugin.rb: 79:in `install_ri_yard_orig' /usr/local/lib/ruby/gems/1.8/gems/yard-0.5.2/lib/rubygems_plugin.rb: 79:in `install\_ri\_yard\_orig’ /usr/local/lib/ruby/gems/1.8/gems/yard-0.4.0/lib/rubygems\_plugin.rb: 77:in `install_ri' /usr/local/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:109:in `generate\_ri’ /usr/local/lib/ruby/site\_ruby/1.8/rubygems/commands/ install\_command.rb:144:in `execute' /usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/ install_command.rb:143:in `each’ /usr/local/lib/ruby/site\_ruby/1.8/rubygems/commands/ install\_command.rb:143:in `execute' /usr/local/lib/ruby/site_ruby/1.8/rubygems/command.rb:257:in `invoke’ /usr/local/lib/ruby/site\_ruby/1.8/rubygems/command\_manager.rb:132:in `process_args' /usr/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run’ /usr/local/lib/ruby/site\_ruby/1.8/rubygems/gem\_runner.rb:58:in `run’ /usr/local/bin/gem:21 I’ll report this to the yard dev. Regards, Dan