From: stan.kaufman@... Date: 2020-02-07T00:37:19+00:00 Subject: [ruby-core:97079] [Ruby master Bug#16613] Vagrant encounters segmentation fault when starting previously correctly working box Issue #16613 has been reported by skaufman (Stan Kaufman). ---------------------------------------- Bug #16613: Vagrant encounters segmentation fault when starting previously correctly working box https://bugs.ruby-lang.org/issues/16613 * Author: skaufman (Stan Kaufman) * Status: Open * 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: