Yes... This is a macro expansion glitch. Basically if `zero` was an integer constant expression (which it isn't, by the way, in your diff), `__buiitin_constant_p` in [this] line would be true, and `rb_define_method` macro would be ex...shyouhei (Shyouhei Urabe)
Found this SEGV using bootsnap. This could well be architecture dependent because of ISeqs being so by nature. Also this doesn't happen when the ISeq is created using `compile_prism`. ``` $ ruby -ve 'RubyVM::InstructionSequence...shyouhei (Shyouhei Urabe)
StringIO situation is different, but for an IO to be read it has to be writable; thus can not be frozen. See what OpenSSL people say aobut this: https://github.com/openssl/openssl/commit/b1d6e3f551ce7e081ed3e30d525253042ebb10a4shyouhei (Shyouhei Urabe)
There's not much thing we can do to this situation. Your file system opted to provide us multiple file paths for an identical content. That's how your operating system is designed to work. Ruby doesn't prevent you from shooting yourse...shyouhei (Shyouhei Urabe)
One thing pointed out in the last developer meeting was that future MMTK might want to break "asprintf return values can be reclaimable using ruby_xfree" assumption at process startup, by choosing different memory management schemes.shyouhei (Shyouhei Urabe)
Thank you for the report anyways! It's totally fine. The io-console build log reads that it builds against ruby 3.1, which is a bit older than C23. It didn't know the breaking C change. It's now continuously integrated against (c...shyouhei (Shyouhei Urabe)
Let there be rooms for each GC implementations how to handle multi threaded situations. They can be totally reentrant, or can have their own mutex, or can rely on rb_thread_call_with_gvl. In any ways the allocator (has been, but now of...shyouhei (Shyouhei Urabe)