nagachika (Tomoyuki Chikanaga) wrote in #note-14: > Do you know the issue was reproducible on ruby-3.4.7 or master branch? Yes, the issue can be reproduced at master branch (`529dd8d76efbe655fabce8933852504851266b2b`) and ruby_3_4 ta...kurly (Greg Kubaryk)
alanwu (Alan Wu) wrote in #note-5: > It's surprising that leaving the temporary struct uninitialized avoids the crash. Smells like a GCC bug or some UB on our end the optimizer is exploiting. > ... Per a suggestion on the downstream bu...kurly (Greg Kubaryk)
alanwu (Alan Wu) wrote in #note-5: > It's surprising that leaving the temporary struct uninitialized avoids the crash. Smells like a GCC bug or some UB on our end the optimizer is exploiting. > ... It doesn't appear to, when added to C...kurly (Greg Kubaryk)
I manually bisected inside that "bad" commit and found that this minimal diff on top of v3_3_10 eliminates the build failure: ``` diff --git a/include/ruby/internal/core/rstring.h b/include/ruby/internal/core/rstring.h index 9cf9daa...kurly (Greg Kubaryk)
Thank you for fixing the markdown in the comment 0. On an affected machine, I was able to bisect the git repo between tags v3_3_9 and v3_3_10: ``` 5a8d7642168f4ea0d9331fded3033c225bbc36c5 is the first bad commit commit 5a8d7642168f...kurly (Greg Kubaryk)
ref downstream bug https://bugs.gentoo.org/965095 - reporting upstream because I was able to reproduce the problem from ruby-3.3.10.tar.xz manually build log excerpt; the rest will be provided as an attachment ``` gcc -O2 -pipe -m...kurly (Greg Kubaryk)
kurly (Greg Kubaryk)05:16 AM Ruby Bug #21655: segfault when building 3.3.10 with GCC 15.2.1, regression from 3.3.9