Open kbaum opened 12 years ago
Thanks, is this a consistent segfault or only occassional? and if it's occasional how rare is it?
Also if you removed ruby-debug did the segfault disappear?
It's consistent when i had ruby-debug.
When I took it away, things worked perfectly. I have some crazy pre-release version of ruby-debug with all of the problems with ruby-1.9.3. Not sure if that has something to do with it.
thx!
@kbaum thanks for the feedback, both ruby-debug and plymouth do some very aggressive things to the ruby runtime so i am not too surprised something bad happened ;) I will look into it however, thanks a bunch and i hope you're enjoying plymouth :)
Been trying plymouth again but would really love to see it work with spork. Not sure if it's possible but otherwise my rails load time is just too long...
I know this is probably annoying as it is probably due to a combination of things, but i'd rather tell you about it than not. When i added to my Gemfile i ended up with a segfault:
I am using ruby-1.9.3 on osx.