[#119132] Segfault using ruby C on MacOS (Intel Catalina and M2 Sonoma) — "martin.kufner--- via ruby-core" <ruby-core@...>
Hey guys,
4 messages
2024/09/12
[#119133] Re: Segfault using ruby C on MacOS (Intel Catalina and M2 Sonoma)
— "martin.kufner--- via ruby-core" <ruby-core@...>
2024/09/12
I just saw, that the #includes dont show up in the c file ...
[#119145] [Ruby master Misc#20728] Propose Eileen Uchitelle as a core committer — "kddnewton (Kevin Newton) via ruby-core" <ruby-core@...>
Issue #20728 has been reported by kddnewton (Kevin Newton).
14 messages
2024/09/12
[#119312] [Ruby master Bug#20762] `make test-basic` with -DRGENGC_FORCE_MAJOR_GC is always failure — "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@...>
Issue #20762 has been reported by hsbt (Hiroshi SHIBATA).
6 messages
2024/09/27
[ruby-core:119171] Re: Segfault using ruby C on MacOS (Intel Catalina and M2 Sonoma)
From:
"martin.kufner--- via ruby-core" <ruby-core@...>
Date:
2024-09-13 08:28:49 UTC
List:
ruby-core #119171
Update: I read that "the Ruby VM is not at all thread safe" according to http://silverhammermba.github.io/emberb/c/#ruby-in-c-threads And I could reproduce that ass soon as I call rb_p in a C pthread it crashes/hangs. My questions: - Is this true for the current Ruby 3.x.x ? - If so are there plans to make Ruby thread safe ? - Is there a workaround except creating a ruby thread in C ? Thanks, Martin ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/