[#104004] [Ruby master Feature#17883] Load bundler/setup earlier to make `bundle exec ruby -r` respect Gemfile — mame@...
Issue #17883 has been reported by mame (Yusuke Endoh).
21 messages
2021/05/24
[ruby-core:103925] [Ruby master Bug#17875] Segfault when reusing a closed Fiber scheduler inside a Thread
From:
rdmosolgo@...
Date:
2021-05-20 20:46:21 UTC
List:
ruby-core #103925
Issue #17875 has been updated by rmosolgo (Robert Mosolgo). Ah, yes, thanks for linking back to that. It sure looks like the same thing. I searched for "fiber scheduler segfault" and didn't find it, but I see it calls it "segv" instead. Please feel free to close this one if it's not useful (I'm not sure if it's useful or not). ---------------------------------------- Bug #17875: Segfault when reusing a closed Fiber scheduler inside a Thread https://bugs.ruby-lang.org/issues/17875#change-92055 * Author: rmosolgo (Robert Mosolgo) * Status: Open * Priority: Normal * ruby -v: 3.0.1 * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN ---------------------------------------- Hi! I've been trying to learn the new `Fiber.scheduler` API. I ran into this segfault when I was misusing scheduler instances in Minitest. I was able to reproduce the bug in isolation and I thought I'd share it here in case it's helpful to anyone. I attached the program as `scheduler_bug.rb` and the output in `bug_output.txt`. I expected this program to terminate with an error, but not with a segfault. If there's anything else I can do to help, please let me know! Thanks, Robert ---Files-------------------------------- scheduler_bug.rb (4.92 KB) bug_output.txt (24.1 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>