DEV Community

Discussion on: Ruby Segmentation Fault When Running RSpec

Collapse
katafrakt profile image
Paweł Świątkowski

It's really hard to tell. In my experience segmentation faults usually happen when there is something wrong with some C extension in some gem. But in your case it seems to come straight from Ruby core lib. Someone might have better idea, but to me it seems like one of those:

  • There is a problem with your Ruby installation (unlikely)
  • Some gem you used accessed some memory it should not, hence this odd backtrace – maybe post your Gemfile
  • Some other program running on your computer messed up something in memory

Not sure if that helps, but that's all I can think of at the moment.

Collapse
andy profile image
Andy Zhao (he/him) Author

Definitely helpful, thanks for the insight. I did reinstall my Ruby and rbenv recently to test something, and ever since then I've been getting that error.

I'm a bit skeptical about this, but it might also be because I upgraded my Mac to High Sierra...

Collapse
katafrakt profile image
Paweł Świątkowski

MacOS is actually notorious for breaking Ruby-related things on every upgrade, so you might be on to something. Just last week my colleague had to reinstall his system completely in order to make Ruby working again. He had other symptoms though, as far as I remember (something SSL-related).

Thread Thread
andy profile image
Andy Zhao (he/him) Author

Yikes. I'm going to be wiping my drive anyway, so while drastic, it might solve my issues. Maybe 2.5.1 will fare better with High Sierra, too.