Skip to content
This repository has been archived by the owner. It is now read-only.

Bundle crashes in Cygwin: Unfortunately, a fatal error has occurred: stack level too deep (SystemStackError) #2281

Closed
starrychloe opened this issue Jan 29, 2013 · 8 comments

Comments

@starrychloe
Copy link

@starrychloe starrychloe commented Jan 29, 2013

Here is the info requested.
https://gist.github.com/4660723

The project is the sample project from RailsInstaller, and modified from http://ruby.railstutorial.org/ruby-on-rails-tutorial-book. I can't use RailsInstaller because another project requires rmagick, which won't install. RailsInstaller directory is renamed, so there are no conflicts. I didn't include Gemfile.lock because you asked me to delete it. I don't know what the boot.rb, preinitializer.rb, environment.rb files are.

@indirect
Copy link
Member

@indirect indirect commented Jan 29, 2013

Hi. Where is the rest of your backtrace?

/usr/lib/ruby/gems/1.9.1/gems/bundler-1.2.3/lib/bundler/friendly_errors.rb:32: stack level too deep (SystemStackError)

is only the first line of the backtrace -- I need to see the rest.

@starrychloe
Copy link
Author

@starrychloe starrychloe commented Jan 29, 2013

I don't know. It didn't print it out. I copied everything.

@rohit
Copy link
Contributor

@rohit rohit commented Jan 29, 2013

That is correct. A stack explosion won't cause the backtrace to be printed out because it will be just the function calling itself.

I guess the only way to figure this out would be to step through bundler in a debugger?

One more way might be to modify friendly_errors.rb to not raise the error but print it and exit. That might give a clue about what is happening?

@indirect
Copy link
Member

@indirect indirect commented Jan 29, 2013

@starrychloe oh, shoot. @rohit is totally right, and that was it. sorry for the misleading message. I'm not sure what could be causing this, but I will see if it's possible to prevent getting caught in a loop.

@starrychloe
Copy link
Author

@starrychloe starrychloe commented Jan 30, 2013

Steps to reproduce, test case:
http://cygwin.com

setup.exe # Install Cygwin and Ruby
gem install rails
rails new testapp # error
rails -v
cd testapp
rails -v # error

@indirect
Copy link
Member

@indirect indirect commented Jan 30, 2013

what happens if you cd testapp and then run bundle install?

On Jan 29, 2013, at 6:05 PM, starrychloe notifications@github.com wrote:

Steps to reproduce, test case:
http://cygwin.com

setup.exe # Install Cygwin and Ruby
gem install rails
rails new testapp # error
rails -v
cd testapp
rails -v # error


Reply to this email directly or view it on GitHub.

@starrychloe
Copy link
Author

@starrychloe starrychloe commented Jan 30, 2013

rails new app will run bundle install automatically. Here it is by itself

Chloe@dumbopc /cygdrive/c/Sites/testapp
$ bundle install
Fetching gem metadata from https://rubygems.org/...........
Fetching gem metadata from https://rubygems.org/..
Unfortunately, a fatal error has occurred. Please see the Bundler
troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
/usr/lib/ruby/gems/1.9.1/gems/bundler-1.2.3/lib/bundler/friendly_errors.rb:32: stack level too deep (SystemStackError)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants