Bundle crashes in Cygwin: Unfortunately, a fatal error has occurred: stack level too deep (SystemStackError) #2281
Comments
Hi. Where is the rest of your backtrace?
is only the first line of the backtrace -- I need to see the rest. |
I don't know. It didn't print it out. I copied everything. |
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 |
@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. |
Steps to reproduce, test case: setup.exe # Install Cygwin and Ruby |
what happens if you On Jan 29, 2013, at 6:05 PM, starrychloe notifications@github.com wrote:
|
Chloe@dumbopc /cygdrive/c/Sites/testapp |
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.
The text was updated successfully, but these errors were encountered: