[#97063] [Ruby master Bug#16608] ConditionVariable#wait should return false when timeout exceeded — shugo@...

Issue #16608 has been reported by shugo (Shugo Maeda).

10 messages 2020/02/05

[#97084] [Ruby master Feature#16614] New method cache mechanism for Guild — ko1@...

Issue #16614 has been reported by ko1 (Koichi Sasada).

18 messages 2020/02/07

[#97248] [Ruby master Bug#16651] Extensions Do Not Compile on Mingw64 — cfis@...

Issue #16651 has been reported by cfis (Charlie Savage).

17 messages 2020/02/24

[#97289] [Ruby master Bug#16658] `method__cache__clear` DTrace hook was dropped without replacement — v.ondruch@...

Issue #16658 has been reported by vo.x (Vit Ondruch).

9 messages 2020/02/27

[#97307] [Ruby master Feature#16663] Add block or filtered forms of Kernel#caller to allow early bail-out — headius@...

Issue #16663 has been reported by headius (Charles Nutter).

29 messages 2020/02/28

[#97310] [Ruby master Feature#16665] Add an Array#except_index method — alexandr1golubenko@...

Issue #16665 has been reported by alex_golubenko (Alex Golubenko).

12 messages 2020/02/29

[ruby-core:97080] [Ruby master Bug#16613] Vagrant encounters segmentation fault when starting previously correctly working box

From: merch-redmine@...
Date: 2020-02-07 01:00:49 UTC
List: ruby-core #97080
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:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next