Issue #19584 has been updated by peterzhu2118 (Peter Zhu). Well, unfortunately it looks like that requirement is not being followed by gems and even in parts of the Ruby codebase. Ruby: - https://github.com/ruby/ruby/blob/fb822076d79339427648cb9eacf76528f827427e/s... - https://github.com/ruby/ruby/blob/fb822076d79339427648cb9eacf76528f827427e/r... Gems: - https://github.com/google/mysql-protobuf/blob/467cda676afaa49e762c5c9164a43f... - https://github.com/ged/ruby-pg/blob/a99322a7111064aec6e430abb8787fa10fce37dd... - https://github.com/rgeo/rgeo/blob/3358e982d277965cfa039fa06a73dd5e2ddcdbdc/e... ---------------------------------------- Bug #19584: Crash in rb_gc_register_address https://bugs.ruby-lang.org/issues/19584#change-102693 * Author: peterzhu2118 (Peter Zhu) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- GitHub PR: https://github.com/ruby/ruby/pull/7670 Some C extensions pass a pointer to a global variable to rb_gc_register_address. However, if a GC is triggered inside of rb_gc_register_address, then the object could get swept since it does not exist on the stack. -- https://bugs.ruby-lang.org/

Issue #19584 has been updated by Eregon (Benoit Daloze). FYI this function is quite difficult to implement on TruffleRuby/other Rubies with the semantics of being called before the assignment. If it's done during `Init_myextension`, we can simulate it, but if it's not we have to read the value immediately for TruffleRuby: https://github.com/oracle/truffleruby/issues/2721 There is no way to hook into the GC to make it read such variables during GC (on JVM at least). This requirement seems documented but one need to read it very carefully to notice it: https://github.com/ruby/ruby/blob/671cfc20000db024f2aeaf602b1a77895c819abc/i... ---------------------------------------- Bug #19584: Crash in rb_gc_register_address https://bugs.ruby-lang.org/issues/19584#change-102703 * Author: peterzhu2118 (Peter Zhu) * Status: Closed * Priority: Normal * Backport: 3.0: REQUIRED, 3.1: REQUIRED, 3.2: REQUIRED ---------------------------------------- GitHub PR: https://github.com/ruby/ruby/pull/7670 Some C extensions pass a pointer to a global variable to rb_gc_register_address. However, if a GC is triggered inside of rb_gc_register_address, then the object could get swept since it does not exist on the stack. -- https://bugs.ruby-lang.org/

Issue #19584 has been updated by hsbt (Hiroshi SHIBATA). Backport changed from 3.0: REQUIRED, 3.1: REQUIRED, 3.2: REQUIRED to 3.0: REQUIRED, 3.1: REQUIRED, 3.2: DONE ruby_3_2 commit:8c3ebe6a00b1176c37bc7894a4373774255f6290 merged revision(s) commit:bccec7fb468ad977be75e7e4c2644b4ea845ab0c, commit:5f8ebcada099351acbc22db264e7cd3773c2bdc4, commit:e13575bb7938e9e5b6a79bfca1b3793123f479da, commit:4adcfc8cd7a17593a6590025da2b03eebf4fd63c. ---------------------------------------- Bug #19584: Crash in rb_gc_register_address https://bugs.ruby-lang.org/issues/19584#change-112283 * Author: peterzhu2118 (Peter Zhu) * Status: Closed * Backport: 3.0: REQUIRED, 3.1: REQUIRED, 3.2: DONE ---------------------------------------- GitHub PR: https://github.com/ruby/ruby/pull/7670 Some C extensions pass a pointer to a global variable to rb_gc_register_address. However, if a GC is triggered inside of rb_gc_register_address, then the object could get swept since it does not exist on the stack. -- https://bugs.ruby-lang.org/