Issue #16613 has been updated by jeremyevans0 (Jeremy Evans).

Status changed from Open to Feedback

Ruby 2.3 is no longer supported.  Does the error still occur if you update to Ruby 2.5, 2.6, or 2.7?

FWIW, it appears to have crashed when updating the access and modification times of files.

----------------------------------------
Bug #16613: Vagrant encounters segmentation fault when starting previously correctly working box
https://bugs.ruby-lang.org/issues/16613#change-84188

* Author: skaufman (Stan Kaufman)
* Status: Feedback
* Priority: Normal
* ruby -v: ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
Have four identical vagrant boxes for staging of Rails sites. All have functioned fine, including three of them today. However, one box segfaults on startup. See attached crash report, which concludes "You may have encountered a bug in the Ruby interpreter or extension libraries." All this is well above my pay grade, but I wonder if somehow this box has become corrupted. Any ideas? Many thanks indeed for any help!

---Files--------------------------------
ruby_2020-02-06-162231_MrFlibble.crash (43.2 KB)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>