April 2025 - ruby-core - ml.ruby-lang.org

[ruby-core:121696] [Ruby Bug#21276] Regression segfault instead of exception `require': cannot load such file
by wsfulton (William Fulton) 22 Apr '25

22 Apr '25

Issue #21276 has been reported by wsfulton (William Fulton). ---------------------------------------- Bug #21276: Regression segfault instead of exception `require': cannot load such file https://bugs.ruby-lang.org/issues/21276 * Author: wsfulton (William Fulton) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- A segfault occurs instead of a Ruby exception in one or the test cases we have in SWIG. I've run a git bisect on the 3.2 releases to identify commit 2aaa9af75989bb0993a44e9690ed2ca890b2ff91 for when the segfault begins: commit 2aaa9af75989bb0993a44e9690ed2ca890b2ff91 Author: nagachika <nagachika(a)ruby-lang.org> Date: Thu Nov 9 17:36:42 2023 +0900 merge revision(s) 4329554f171fdb483cafa672df5f2a08741940c5,b5c74d548872388921402ff2db36be15e924a89b: [Backport #19985] [Bug #19985] Raise LoadError with the converted feature name `Kernel#require` converts feature name objects that have the `to_path` method such as `Pathname`, but had used the original object on error and had resulted in an unexpected `TypeError`. --- load.c | 14 +++++++++++--- test/ruby/test_require.rb | 26 +++++++++++++++++++++----- 2 files changed, 32 insertions(+), 8 deletions(-) Ease the `Encoding::CompatibilityError` test failure At the time this test first started using `assert_raise_with_message`, it did not touch `Encoding.default_internal`. --- test/ruby/test_require.rb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) So, ruby-3.2.2 is okay and 3.2.3 has the regression. Still present with ruby-3.2.8. I'll provide two ways to replicate. 1. Using SWIG built from source: 1a. clone SWIG from github and build SWIG using steps 1. and 2. from https://swig.org/svn.html. Note that you can specify a custom build of ruby to use with: ./configure --with-ruby=/my-path-to-ruby-installation/bin/ruby 1b. cd Examples/test-suite/ruby 1c. make import_fragments.cpptest CXXFLAGS=-g This is my output using ruby version 3.2.3 (ruby git tag v3_2_3): ~/swig/github/wsfulton/swig/Examples/test-suite/ruby (master >)$ make import_fragments.cpptest CXXFLAGS=-g if [ -f ./import_fragments_runme.rb ]; then echo "checking ruby testcase import_fragments (with run test)" ; else echo "checking ruby testcase import_fragments" ; fi checking ruby testcase import_fragments (with run test) make -f ../../../Examples/Makefile SRCDIR='./' CXXSRCS='' SWIG_LIB_DIR='../../../Lib' SWIGEXE='../../../swig' INCLUDES='-I../../../Examples/test-suite' SWIGOPT='-outcurrentdir -I../../../Examples/test-suite -w801 -noautorename -features autodoc=4 -Werror' NOLINK=true TARGET='import_fragments' INTERFACEDIR='../' INTERFACE='import_fragments.i' ruby_cpp make[1]: Entering directory '/home/william/swig/github/wsfulton/swig/Examples/test-suite/ruby' env SWIG_LIB=../../../Lib ../../../swig -c++ -ruby -outcurrentdir -I../../../Examples/test-suite -w801 -noautorename -features autodoc=4 -Werror -o import_fragments_wrap.cxx ./../import_fragments.i g++ -c -fPIC -I. -I./ -g -fPIC import_fragments_wrap.cxx -I../../../Examples/test-suite -I/home/william/install/ruby-3_2_3-debug/include/ruby-3.2.0 -I/home/william/install/ruby-3_2_3-debug/include/ruby-3.2.0/x86_64-linux g++ -shared -g import_fragments_wrap.o -o import_fragments.so make[1]: Leaving directory '/home/william/swig/github/wsfulton/swig/Examples/test-suite/ruby' if [ -f ./import_fragments_runme.rb ]; then env LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH /home/william/install/ruby-3_2_3-debug/bin/ruby -I.:. ./import_fragments_runme.rb; elif [ -f ./import_fragments.so ] ; then env LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH /home/william/install/ruby-3_2_3-debug/bin/ruby -I.:. -r./import_fragments.so -e '' ; fi <internal:/home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:151: [BUG] Segmentation fault at 0x000000000000000a ruby 3.2.3 (2024-01-18 revision 52bb2ac0a6) [x86_64-linux] -- Control frame information ----------------------------------------------- c:0004 p:0018 s:0029 e:000026 RESCUE <internal:/home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:151 c:0003 p:0275 s:0023 e:000022 METHOD <internal:/home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:40 c:0002 p:0014 s:0008 E:002010 EVAL ./import_fragments_runme.rb:15 [FINISH] c:0001 p:0000 s:0003 E:000bf0 DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- ./import_fragments_runme.rb:15:in `<main>' <internal:/home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:40:in `require' <internal:/home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:151:in `rescue in require' -- Machine register context ------------------------------------------------ RIP: 0x000057fa8949081d RBP: 0x00007ffdd0182518 RSP: 0x00007ffdd0182518 RAX: 0x000000000000000a RBX: 0x000057fa94261250 RCX: 0x000000000000008c RDX: 0x000000000000008c RDI: 0x000000000000000a RSI: 0x000000000000008c R8: 0x0000000000000845 R9: 0x0000000000000020 R10: 0x000057fa94071fc0 R11: 0x0000000000000040 R12: 0x0000000000000003 R13: 0x0000000000000000 R14: 0x000057fa94261260 R15: 0x00007b246ad86f10 EFL: 0x0000000000010283 -- C level backtrace information ------------------------------------------- /home/william/install/ruby-3_2_3-debug/bin/ruby(rb_print_backtrace+0x20) [0x57fa8950f75c] ../vm_dump.c:785 /home/william/install/ruby-3_2_3-debug/bin/ruby(rb_vm_bugreport+0x198) [0x57fa8950fd07] ../vm_dump.c:1080 /home/william/install/ruby-3_2_3-debug/bin/ruby(rb_bug_for_fatal_signal+0x12c) [0x57fa895b3000] /home/william/install/ruby-3_2_3-debug/bin/ruby(sigsegv+0x74) [0x57fa8945b1be] ../signal.c:964 /home/william/install/ruby-3_2_3-debug/bin/ruby(sigill) (null):0 /lib/x86_64-linux-gnu/libc.so.6(0x7b246aa45330) [0x7b246aa45330] /home/william/install/ruby-3_2_3-debug/bin/ruby(hash_table_index+0x13) [0x57fa8949081d] ../id_table.c:132 /home/william/install/ruby-3_2_3-debug/bin/ruby(rb_id_table_lookup+0x38) [0x57fa89490bb5] ../id_table.c:230 /home/william/install/ruby-3_2_3-debug/bin/ruby(vm_search_cc+0x6e) [0x57fa894db233] ../vm_insnhelper.c:1988 /home/william/install/ruby-3_2_3-debug/bin/ruby(rb_vm_search_method_slowpath+0x51) [0x57fa894db4b3] ../vm_insnhelper.c:2084 /home/william/install/ruby-3_2_3-debug/bin/ruby(vm_search_method_slowpath0+0x2e) [0x57fa894db51a] ../vm_insnhelper.c:2106 /home/william/install/ruby-3_2_3-debug/bin/ruby(vm_search_method_fastpath+0x66) [0x57fa894db614] ../vm_insnhelper.c:2172 /home/william/install/ruby-3_2_3-debug/bin/ruby(vm_search_method) ../vm_insnhelper.c:2182 /home/william/install/ruby-3_2_3-debug/bin/ruby(vm_method_cfunc_is+0x2f) [0x57fa894db693] ../vm_insnhelper.c:2237 /home/william/install/ruby-3_2_3-debug/bin/ruby(opt_equality+0x6a) [0x57fa894db990] ../vm_insnhelper.c:2324 /home/william/install/ruby-3_2_3-debug/bin/ruby(vm_exec_core+0x5983) [0x57fa894efa06] ../insns.def:1174 /home/william/install/ruby-3_2_3-debug/bin/ruby(rb_vm_exec+0x1a8) [0x57fa8950499c] ../vm.c:2383 /home/william/install/ruby-3_2_3-debug/bin/ruby(rb_iseq_eval_main+0x42) [0x57fa89505731] ../vm.c:2633 /home/william/install/ruby-3_2_3-debug/bin/ruby(rb_ec_exec_node+0x125) [0x57fa892deeb9] ../eval.c:289 /home/william/install/ruby-3_2_3-debug/bin/ruby(ruby_run_node+0x96) [0x57fa892df026] ../eval.c:330 /home/william/install/ruby-3_2_3-debug/bin/ruby(rb_main+0x4c) [0x57fa892da455] ../main.c:38 /home/william/install/ruby-3_2_3-debug/bin/ruby(main+0x62) [0x57fa892da4cd] ../main.c:57 -- Other runtime information ----------------------------------------------- * Loaded script: ./import_fragments_runme.rb * Loaded features: 0 enumerator.so 1 thread.rb 2 fiber.so 3 rational.so 4 complex.so 5 ruby2_keywords.rb 6 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/encdb.so 7 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/trans/transdb.so 8 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/rbconfig.rb 9 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/compatibility.rb 10 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/defaults.rb 11 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/deprecate.rb 12 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/errors.rb 13 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/unknown_command_spell_checker.rb 14 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/exceptions.rb 15 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/basic_specification.rb 16 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/stub_specification.rb 17 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/platform.rb 18 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/util/list.rb 19 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/version.rb 20 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/requirement.rb 21 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/specification.rb 22 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/util.rb 23 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems/core_ext/kernel_gem.rb 24 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/monitor.so 25 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/monitor.rb 26 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/rubygems.rb 27 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/error_highlight/version.rb 28 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/error_highlight/base.rb 29 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/error_highlight/formatter.rb 30 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/error_highlight/core_ext.rb 31 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/error_highlight.rb 32 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/version.rb 33 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/core_ext/name_error.rb 34 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/levenshtein.rb 35 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/jaro_winkler.rb 36 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/spell_checker.rb 37 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/spell_checkers/name_error_checkers/class_name_checker.rb 38 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/spell_checkers/name_error_checkers/variable_name_checker.rb 39 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/spell_checkers/name_error_checkers.rb 40 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/spell_checkers/method_name_checker.rb 41 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/spell_checkers/key_error_checker.rb 42 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/spell_checkers/null_checker.rb 43 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/tree_spell_checker.rb 44 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/spell_checkers/require_path_checker.rb 45 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/spell_checkers/pattern_key_name_checker.rb 46 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean/formatter.rb 47 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/did_you_mean.rb 48 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/syntax_suggest/core_ext.rb 49 /home/william/swig/github/wsfulton/swig/Examples/test-suite/ruby/swig_assert.rb * Process memory map: 57fa892aa000-57fa892d9000 r--p 00000000 103:06 30818930 /home/william/install/ruby-3_2_3-debug/bin/ruby 57fa892d9000-57fa895c5000 r-xp 0002f000 103:06 30818930 /home/william/install/ruby-3_2_3-debug/bin/ruby 57fa895c5000-57fa8974e000 r--p 0031b000 103:06 30818930 /home/william/install/ruby-3_2_3-debug/bin/ruby 57fa8974e000-57fa89757000 r--p 004a4000 103:06 30818930 /home/william/install/ruby-3_2_3-debug/bin/ruby 57fa89757000-57fa89758000 rw-p 004ad000 103:06 30818930 /home/william/install/ruby-3_2_3-debug/bin/ruby 57fa89758000-57fa8976d000 rw-p 00000000 00:00 0 57fa94047000-57fa9435c000 rw-p 00000000 00:00 0 [heap] 7b2464200000-7b2464407000 r--s 00000000 103:04 407927 /usr/lib/x86_64-linux-gnu/libc.so.6 7b2464600000-7b24650bb000 r--s 00000000 103:06 30818930 /home/william/install/ruby-3_2_3-debug/bin/ruby 7b2465200000-7b246529d000 r--p 00000000 103:04 408519 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33 7b246529d000-7b24653e5000 r-xp 0009d000 103:04 408519 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33 7b24653e5000-7b246546c000 r--p 001e5000 103:04 408519 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33 7b246546c000-7b2465477000 r--p 0026b000 103:04 408519 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33 7b2465477000-7b246547a000 rw-p 00276000 103:04 408519 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33 7b246547a000-7b246547e000 rw-p 00000000 00:00 0 7b24655b7000-7b24655b8000 ---p 00000000 00:00 0 7b24655b8000-7b2465659000 rw-p 00000000 00:00 0 7b2465659000-7b246565a000 ---p 00000000 00:00 0 7b246565a000-7b24656fb000 rw-p 00000000 00:00 0 7b24656fb000-7b24656fc000 ---p 00000000 00:00 0 7b24656fc000-7b246579d000 rw-p 00000000 00:00 0 7b246579d000-7b246579e000 ---p 00000000 00:00 0 7b246579e000-7b246583f000 rw-p 00000000 00:00 0 7b246583f000-7b2465840000 ---p 00000000 00:00 0 7b2465840000-7b24658e1000 rw-p 00000000 00:00 0 7b24658e1000-7b24658e2000 ---p 00000000 00:00 0 7b24658e2000-7b2465983000 rw-p 00000000 00:00 0 7b2465983000-7b2465984000 ---p 00000000 00:00 0 7b2465984000-7b2465a25000 rw-p 00000000 00:00 0 7b2465a25000-7b2465a26000 ---p 00000000 00:00 0 7b2465a26000-7b2465ac7000 rw-p 00000000 00:00 0 7b2465ac7000-7b2465ac8000 ---p 00000000 00:00 0 7b2465ac8000-7b2465b69000 rw-p 00000000 00:00 0 7b2465b69000-7b2465b6a000 ---p 00000000 00:00 0 7b2465b6a000-7b2465c0b000 rw-p 00000000 00:00 0 7b2465c0b000-7b2465c0c000 ---p 00000000 00:00 0 7b2465c0c000-7b2465cad000 rw-p 00000000 00:00 0 7b2465cad000-7b2465cae000 ---p 00000000 00:00 0 7b2465cae000-7b2465d4f000 rw-p 00000000 00:00 0 7b2465d4f000-7b2465d50000 ---p 00000000 00:00 0 7b2465d50000-7b2465df1000 rw-p 00000000 00:00 0 7b2465df1000-7b2465df2000 ---p 00000000 00:00 0 7b2465df2000-7b2465e93000 rw-p 00000000 00:00 0 7b2465e93000-7b2465e94000 ---p 00000000 00:00 0 7b2465e94000-7b2465f35000 rw-p 00000000 00:00 0 7b2465f35000-7b2465f36000 ---p 00000000 00:00 0 7b2465f36000-7b2465fd7000 rw-p 00000000 00:00 0 7b2465fd7000-7b2465fd8000 ---p 00000000 00:00 0 7b2465fd8000-7b2466079000 rw-p 00000000 00:00 0 7b2466079000-7b246607a000 ---p 00000000 00:00 0 7b246607a000-7b246611b000 rw-p 00000000 00:00 0 7b246611b000-7b246611c000 ---p 00000000 00:00 0 7b246611c000-7b24661bd000 rw-p 00000000 00:00 0 7b24661bd000-7b24661be000 ---p 00000000 00:00 0 7b24661be000-7b246625f000 rw-p 00000000 00:00 0 7b246625f000-7b2466260000 ---p 00000000 00:00 0 7b2466260000-7b2466301000 rw-p 00000000 00:00 0 7b2466301000-7b2466302000 ---p 00000000 00:00 0 7b2466302000-7b24663a3000 rw-p 00000000 00:00 0 7b24663a3000-7b24663a4000 ---p 00000000 00:00 0 7b24663a4000-7b2466445000 rw-p 00000000 00:00 0 7b2466445000-7b2466446000 ---p 00000000 00:00 0 7b2466446000-7b24664e7000 rw-p 00000000 00:00 0 7b24664e7000-7b24664e8000 ---p 00000000 00:00 0 7b24664e8000-7b2466589000 rw-p 00000000 00:00 0 7b2466589000-7b246658a000 ---p 00000000 00:00 0 7b246658a000-7b246662b000 rw-p 00000000 00:00 0 7b246662b000-7b246662c000 ---p 00000000 00:00 0 7b246662c000-7b24666cd000 rw-p 00000000 00:00 0 7b24666cd000-7b24666ce000 ---p 00000000 00:00 0 7b24666ce000-7b246676f000 rw-p 00000000 00:00 0 7b246676f000-7b2466770000 ---p 00000000 00:00 0 7b2466770000-7b2466811000 rw-p 00000000 00:00 0 7b2466811000-7b2466812000 ---p 00000000 00:00 0 7b2466812000-7b24668b3000 rw-p 00000000 00:00 0 7b24668b3000-7b24668b4000 ---p 00000000 00:00 0 7b24668b4000-7b2466955000 rw-p 00000000 00:00 0 7b2466955000-7b2466956000 ---p 00000000 00:00 0 7b2466956000-7b24669f7000 rw-p 00000000 00:00 0 7b24669f7000-7b2469a00000 rw-p 00000000 00:00 0 7b2469a12000-7b2469a16000 r--p 00000000 103:04 408078 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 7b2469a16000-7b2469a3a000 r-xp 00004000 103:04 408078 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 7b2469a3a000-7b2469a3e000 r--p 00028000 103:04 408078 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 7b2469a3e000-7b2469a3f000 r--p 0002b000 103:04 408078 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 7b2469a3f000-7b2469a40000 rw-p 0002c000 103:04 408078 /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 7b2469a40000-7b2469a70000 rw-p 00000000 00:00 0 7b2469aa0000-7b2469b80000 rw-p 00000000 00:00 0 7b2469b8f000-7b2469c00000 rw-p 00000000 00:00 0 7b2469c00000-7b246a9ec000 r--p 00000000 103:04 398501 /usr/lib/locale/locale-archive 7b246aa00000-7b246aa28000 r--p 00000000 103:04 407927 /usr/lib/x86_64-linux-gnu/libc.so.6 7b246aa28000-7b246abb0000 r-xp 00028000 103:04 407927 /usr/lib/x86_64-linux-gnu/libc.so.6 7b246abb0000-7b246abff000 r--p 001b0000 103:04 407927 /usr/lib/x86_64-linux-gnu/libc.so.6 7b246abff000-7b246ac03000 r--p 001fe000 103:04 407927 /usr/lib/x86_64-linux-gnu/libc.so.6 7b246ac03000-7b246ac05000 rw-p 00202000 103:04 407927 /usr/lib/x86_64-linux-gnu/libc.so.6 7b246ac05000-7b246ac12000 rw-p 00000000 00:00 0 7b246ac26000-7b246ac28000 r--p 00000000 103:06 5909120 /home/william/swig/github/wsfulton/swig/Examples/test-suite/ruby/import_fragments.so 7b246ac28000-7b246ac2c000 r-xp 00002000 103:06 5909120 /home/william/swig/github/wsfulton/swig/Examples/test-suite/ruby/import_fragments.so 7b246ac2c000-7b246ac2e000 r--p 00006000 103:06 5909120 /home/william/swig/github/wsfulton/swig/Examples/test-suite/ruby/import_fragments.so 7b246ac2e000-7b246ac2f000 r--p 00007000 103:06 5909120 /home/william/swig/github/wsfulton/swig/Examples/test-suite/ruby/import_fragments.so 7b246ac2f000-7b246ac30000 rw-p 00008000 103:06 5909120 /home/william/swig/github/wsfulton/swig/Examples/test-suite/ruby/import_fragments.so 7b246ac30000-7b246ac80000 rw-p 00000000 00:00 0 7b246ac87000-7b246ad8d000 rw-p 00000000 00:00 0 7b246ad8d000-7b246ad9d000 r--p 00000000 103:04 408271 /usr/lib/x86_64-linux-gnu/libm.so.6 7b246ad9d000-7b246ae1c000 r-xp 00010000 103:04 408271 /usr/lib/x86_64-linux-gnu/libm.so.6 7b246ae1c000-7b246ae74000 r--p 0008f000 103:04 408271 /usr/lib/x86_64-linux-gnu/libm.so.6 7b246ae74000-7b246ae75000 r--p 000e7000 103:04 408271 /usr/lib/x86_64-linux-gnu/libm.so.6 7b246ae75000-7b246ae76000 rw-p 000e8000 103:04 408271 /usr/lib/x86_64-linux-gnu/libm.so.6 7b246ae76000-7b246ae78000 r--p 00000000 103:04 407962 /usr/lib/x86_64-linux-gnu/libcrypt.so.1.1.0 7b246ae78000-7b246ae8d000 r-xp 00002000 103:04 407962 /usr/lib/x86_64-linux-gnu/libcrypt.so.1.1.0 7b246ae8d000-7b246aea6000 r--p 00017000 103:04 407962 /usr/lib/x86_64-linux-gnu/libcrypt.so.1.1.0 7b246aea6000-7b246aea7000 r--p 0002f000 103:04 407962 /usr/lib/x86_64-linux-gnu/libcrypt.so.1.1.0 7b246aea7000-7b246aea8000 rw-p 00030000 103:04 407962 /usr/lib/x86_64-linux-gnu/libcrypt.so.1.1.0 7b246aea8000-7b246aeb0000 rw-p 00000000 00:00 0 7b246aeb0000-7b246aeba000 r--p 00000000 103:04 408107 /usr/lib/x86_64-linux-gnu/libgmp.so.10.5.0 7b246aeba000-7b246af1d000 r-xp 0000a000 103:04 408107 /usr/lib/x86_64-linux-gnu/libgmp.so.10.5.0 7b246af1d000-7b246af32000 r--p 0006d000 103:04 408107 /usr/lib/x86_64-linux-gnu/libgmp.so.10.5.0 7b246af32000-7b246af33000 r--p 00081000 103:04 408107 /usr/lib/x86_64-linux-gnu/libgmp.so.10.5.0 7b246af33000-7b246af34000 rw-p 00082000 103:04 408107 /usr/lib/x86_64-linux-gnu/libgmp.so.10.5.0 7b246af34000-7b246af36000 r--p 00000000 103:04 408661 /usr/lib/x86_64-linux-gnu/libz.so.1.3 7b246af36000-7b246af48000 r-xp 00002000 103:04 408661 /usr/lib/x86_64-linux-gnu/libz.so.1.3 7b246af48000-7b246af4e000 r--p 00014000 103:04 408661 /usr/lib/x86_64-linux-gnu/libz.so.1.3 7b246af4e000-7b246af4f000 r--p 0001a000 103:04 408661 /usr/lib/x86_64-linux-gnu/libz.so.1.3 7b246af4f000-7b246af50000 rw-p 0001b000 103:04 408661 /usr/lib/x86_64-linux-gnu/libz.so.1.3 7b246af56000-7b246af57000 r--p 00000000 103:06 30823100 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/monitor.so 7b246af57000-7b246af58000 r-xp 00001000 103:06 30823100 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/monitor.so 7b246af58000-7b246af59000 r--p 00002000 103:06 30823100 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/monitor.so 7b246af59000-7b246af5a000 r--p 00002000 103:06 30823100 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/monitor.so 7b246af5a000-7b246af5b000 rw-p 00003000 103:06 30823100 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/monitor.so 7b246af5b000-7b246af5c000 r--p 00000000 103:06 31620633 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/trans/transdb.so 7b246af5c000-7b246af5e000 r-xp 00001000 103:06 31620633 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/trans/transdb.so 7b246af5e000-7b246af5f000 r--p 00003000 103:06 31620633 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/trans/transdb.so 7b246af5f000-7b246af60000 r--p 00003000 103:06 31620633 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/trans/transdb.so 7b246af60000-7b246af61000 rw-p 00004000 103:06 31620633 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/trans/transdb.so 7b246af61000-7b246af62000 r--p 00000000 103:06 30818979 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/encdb.so 7b246af62000-7b246af64000 r-xp 00001000 103:06 30818979 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/encdb.so 7b246af64000-7b246af65000 r--p 00003000 103:06 30818979 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/encdb.so 7b246af65000-7b246af66000 r--p 00003000 103:06 30818979 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/encdb.so 7b246af66000-7b246af67000 rw-p 00004000 103:06 30818979 /home/william/install/ruby-3_2_3-debug/lib/ruby/3.2.0/x86_64-linux/enc/encdb.so 7b246af67000-7b246af6e000 r--s 00000000 103:04 409682 /usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache 7b246af6e000-7b246af70000 rw-p 00000000 00:00 0 7b246af70000-7b246af74000 r--p 00000000 00:00 0 [vvar] 7b246af74000-7b246af76000 r-xp 00000000 00:00 0 [vdso] 7b246af76000-7b246af77000 r--p 00000000 103:04 407739 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 7b246af77000-7b246afa2000 r-xp 00001000 103:04 407739 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 7b246afa2000-7b246afac000 r--p 0002c000 103:04 407739 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 7b246afac000-7b246afae000 r--p 00036000 103:04 407739 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 7b246afae000-7b246afb0000 rw-p 00038000 103:04 407739 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 7ffdcf987000-7ffdd0186000 rw-p 00000000 00:00 0 [stack] ffffffffff600000-ffffffffff601000 --xp 00000000 00:00 0 [vsyscall] Aborted (core dumped) make: *** [Makefile:82: import_fragments.cpptest] Error 134 2. Using attached tarball 2a. tar -xf ruby-crash-.tar.bz2 2b. cd ruby-crash 2c. Adjust RUBY_ROOT in Makefile to your Ruby installation 2c. make ---Files-------------------------------- ruby-crash.tar.bz2 (21 KB) -- https://bugs.ruby-lang.org/

2 4

[ruby-core:121698] [Ruby Feature#3388] regexp support for start_with? and end_with?
by Eregon (Benoit Daloze) 21 Apr '25

21 Apr '25

Issue #3388 has been updated by Eregon (Benoit Daloze). `end_with?(/regex/)` if it recreates a Regexp on every call would be extremely slow. Languages with such APIs have learned the hard way it's a mistake to expose such APIs creating a Regexp behind the scenes. One thing that could work is to lazily create and cache inside a Regexp object a variant of it with \z for this purpose. But it would likely increase footprint. ---------------------------------------- Feature #3388: regexp support for start_with? and end_with? https://bugs.ruby-lang.org/issues/3388#change-112750 * Author: trans (Thomas Sawyer) * Status: Feedback * Assignee: naruse (Yui NARUSE) ---------------------------------------- =begin ruby-1.9.2-head > "aBcdeFghIj".start_with?(/abc/i) => false In my implementation of start_with? it is easy enough to utilize #index, which works fine: def start_with?(pattern) index(pattern) == 0 end But #end_with? is more difficult, and I had to use regular expressions. def end_with?(suffix) suffix = Regexp.escape(suffix) if String===suffix /#{suffix}$/.match(self) ? true : false end However, we might get rid of the '? true : false' and return the MatchData, since that could be useful information. =end ---Files-------------------------------- 0001-string.c-rb_str_start_with-rb_str_end_with-allow-Reg.patch (4.08 KB) -- https://bugs.ruby-lang.org/

1 0

[ruby-core:121413] [Ruby Bug#21193] Inherited callback returns `nil` for `Object.const_source_location`
by eileencodes (Eileen Uchitelle) 20 Apr '25

20 Apr '25

Issue #21193 has been reported by eileencodes (Eileen Uchitelle). ---------------------------------------- Bug #21193: Inherited callback returns `nil` for `Object.const_source_location` https://bugs.ruby-lang.org/issues/21193 * Author: eileencodes (Eileen Uchitelle) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Since https://github.com/ruby/ruby/pull/12927 the inherited callback no longer can access the `Object.const_source_location`. A simplified reproduction is the following: ```ruby class A def self.inherited(other) super p Object.const_source_location(other.name) end end class B < A end ``` Prior to this change `Object.const_source_location(other.name)` would return `["test.rb", 8]` and now returns `nil`. Shopify's application uses the `inherited` callback to load configuration classes and since it's unable to find these classes they aren't loaded when they are called. It's not clear if this was intended or if there's a workaround. In chatting with folks at GitHub, they have a similar issue (although that case sounds less straightforward). A more accurate example of what we have (I did strip this down a bunch too): ```ruby def self.inherited(config) return super unless config.superclass == Config if (class_name = config.name) && (config_location = Object.const_source_location(class_name)) && (parent_dirname = File.dirname(config_location[0])) config_dirname = File.join(parent_dirname, "config") config.autoload(:Something, File.join(config_dirname, "something.rb")) end super end ``` Original issue: https://bugs.ruby-lang.org/issues/21143 cc/ @byroot @fxn -- https://bugs.ruby-lang.org/

6 14

[ruby-core:121685] [Ruby Bug#21273] regression on 3.1.7 vs 3.1.2
by rouca (Bastien Roucaries) 20 Apr '25

20 Apr '25

Issue #21273 has been reported by rouca (Bastien Roucaries). ---------------------------------------- Bug #21273: regression on 3.1.7 vs 3.1.2 https://bugs.ruby-lang.org/issues/21273 * Author: rouca (Bastien Roucaries) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Hi, On debian we wish to package the last 3.1 version before EOL unfortunaltly it regress see https://salsa.debian.org/ruby-team/ruby/-/jobs/7430073#L7376 We are clue less could we get some help ? -- https://bugs.ruby-lang.org/

2 4

[ruby-core:121692] [Ruby Feature#3388] regexp support for start_with? and end_with?
by baweaver (Brandon Weaver) 20 Apr '25

20 Apr '25

Issue #3388 has been updated by baweaver (Brandon Weaver). I have admittedly found this confusing recently when I had attempted to use `end_with?(/regex/)` in a book example. Would it be acceptable to consider a non-ideal implementation of this feature, and then continue to optimize it in future releases? I believe the potential confusion relative to its dual method `start_with?` warrants some consideration of consistency in implementation here, even if not enough distinct cases exist exclusively for `end_with?` and regular expressions. ---------------------------------------- Feature #3388: regexp support for start_with? and end_with? https://bugs.ruby-lang.org/issues/3388#change-112743 * Author: trans (Thomas Sawyer) * Status: Feedback * Assignee: naruse (Yui NARUSE) ---------------------------------------- =begin ruby-1.9.2-head > "aBcdeFghIj".start_with?(/abc/i) => false In my implementation of start_with? it is easy enough to utilize #index, which works fine: def start_with?(pattern) index(pattern) == 0 end But #end_with? is more difficult, and I had to use regular expressions. def end_with?(suffix) suffix = Regexp.escape(suffix) if String===suffix /#{suffix}$/.match(self) ? true : false end However, we might get rid of the '? true : false' and return the MatchData, since that could be useful information. =end ---Files-------------------------------- 0001-string.c-rb_str_start_with-rb_str_end_with-allow-Reg.patch (4.08 KB) -- https://bugs.ruby-lang.org/

1 0

[ruby-core:121672] [Ruby Feature#21269] Opt in to raise for modification of chilled strings returned from `Symbol#to_s`
by Earlopain (Earlopain _) 17 Apr '25

17 Apr '25

Issue #21269 has been reported by Earlopain (Earlopain _). ---------------------------------------- Feature #21269: Opt in to raise for modification of chilled strings returned from `Symbol#to_s` https://bugs.ruby-lang.org/issues/21269 * Author: Earlopain (Earlopain _) * Status: Open ---------------------------------------- Ref https://bugs.ruby-lang.org/issues/20350 ```rb begin :foo.to_s << "bar" puts "ok sym" rescue puts "fail sym" end begin "foo" << "bar" puts "ok str" rescue puts "failed str" end ``` Output with `RUBYOPT="--enable=frozen-string-literal -W"`: ``` test.rb:2: warning: string returned by :foo.to_s will be frozen in the future ok sym failed str ``` `--enable=frozen-string-literal` does something for string literals, I would like the same for `Symbol#to_s`. I would suggest simply reusing `--enable=frozen-string-literal` but its name seems very clear about being about string literals, which doesn't really fit for what's going on with symbols here. For convenience, it would be very nice to have just a single switch for this though. -- https://bugs.ruby-lang.org/

2 2

[ruby-core:121670] [Ruby Feature#21268] Implement a lock-free hash set for fstring table
by jhawthorn (John Hawthorn) 17 Apr '25

17 Apr '25

Issue #21268 has been reported by jhawthorn (John Hawthorn). ---------------------------------------- Feature #21268: Implement a lock-free hash set for fstring table https://bugs.ruby-lang.org/issues/21268 * Author: jhawthorn (John Hawthorn) * Status: Open * Assignee: jhawthorn (John Hawthorn) * Target version: 3.5 ---------------------------------------- I would like to propose replacing the st_table used for fstrings (de-duplicated frozen strings) with a lock-free hash set to have improved performance in a Ractor environment. Fstrings are shared between Ractors, and can be looked up concurrently by multiple Ractors, it's desirable to be able to do this work in parallel. There should be no change visible to users (other than improved performance :) ) Previously this table used the VM lock (`RB_VM_LOCK_ENTER`, not the GVL) to serialize access. I first experimented with using a reader-writer lock, but that was a little awkward to use as it was easy to cause a deadlock between the new lock, `RB_VM_LOCK_ENTER`, and `rb_vm_barrier()`. An RW lock also can cause cache ping ponging (though striping can help). Lastly, this table is somewhat write-heavy, so it's desirable for even writes to be possible in parallel. A lock free table is not necessarily faster than a table with locking, but due to these constraints and usage I believe a lock-free table is desirable here. The design is a fairly standard open-addressing hash table with quadratic probing. Similar to our existing st_table or id_table. Deletes (which happen on GC) replace existing keys with a tombstone, which is the only type of update which can occur. Tombstones are only cleared out on rebuilds (necessary for the lock-free design I used). The set is wait-free for lookup (the thread performing lookup always makes progress) and lock-free for insert (we may sometimes retry if another thread made a concurrent insertion, we never spin on a lock) unless resizing/rebuilding. The implementation itself is at https://github.com/ruby/ruby/pull/12921 and details are within. I will include benchmarks in a comment below. -- https://bugs.ruby-lang.org/

1 1

[ruby-core:121674] [Ruby Bug#21270] init_fast_fallback_inetsock_internal (default for TCPSocket.new/TCPSocket.open) isn't fiber aware
by drahosj (Jake Drahos) 16 Apr '25

16 Apr '25

Issue #21270 has been reported by drahosj (Jake Drahos). ---------------------------------------- Bug #21270: init_fast_fallback_inetsock_internal (default for TCPSocket.new/TCPSocket.open) isn't fiber aware https://bugs.ruby-lang.org/issues/21270 * Author: drahosj (Jake Drahos) * Status: Open * ruby -v: ruby 3.4.2 * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Sockets created via `init_fast_fallback_inetsock_internal()` don't get a chance to call the scheduler hook(s). This is the default for connections created with TCPSocket.new unless fast_fallback is specified as false. Unfortunately, this has the effect of blocking all fibers in the thread if the initial connect() call hangs. TCPSocket.open() is used in Net::HTTP, which means the issue is present there. Here's a quick proof of concept. It works as intended as written (starts both fibers even though the first fiber hangs). Switching to the default `TCPSocket.new` call causes the whole thread to block. NOTE: Uses the "toy" scheduler from test/fiber/scheduler.rb, but the Socketry async gem is also affected (should affect all schedulers since the hook isn't called). ``` ruby require 'socket' require_relative 'scheduler' Fiber.set_scheduler(Scheduler.new) puts "#{Fiber.current.object_id}: Main fiber" Fiber.schedule do puts "#{Fiber.current.object_id}: Creating socket" # Assuming that attempting to connect to example.com on port 12345 hangs # Default causes the scheduler to hang and never create second fiber # TCPSocket.new("example.com", 12345) TCPSocket.new("example.com", 12345, fast_fallback: false) puts "#{Fiber.current.object_id}: Connected" end Fiber.schedule do puts "#{Fiber.current.object_id}: Sleeping" sleep 2 puts "#{Fiber.current.object_id}: Done sleeping" end puts "#{Fiber.current.object_id}: Both fibers started" ``` Running the working PoC: ``` shell $ ruby async-connect.rb 16: Main fiber 24: Creating socket 32: Sleeping 16: Both fibers started 32: Done sleeping [Hangs here until the socket connection eventually times out] ``` However, without `fast_fallback: false`, the `TCPSocket.new` call will block the entire scheduler, never creating the second fiber: ``` shell $ ruby async-request.rb 16: Main fiber 24: Creating socket [Hangs here until the connect times out] ``` Here's a stack dump of the hung version: ``` #0 __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56 #1 0x00007fc9e4c9581c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=a5@entry=0, a6=a6@entry=0, nr=270) at cancellation.c:49 #2 0x00007fc9e4c95871 in __syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=a5@entry=0, a6=a6@entry=0, nr=270) at cancellation.c:75 #3 0x00007fc9e4d1af07 in __GI___select (nfds=<optimized out>, readfds=<optimized out>, writefds=<optimized out>, exceptfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/select.c:69 #4 0x00007fc9e5233c9f in rb_fd_select (n=<optimized out>, readfds=<optimized out>, writefds=<optimized out>, exceptfds=<optimized out>, timeout=<optimized out>) at /usr/src/debug/ruby-3.4.2/thread.c:4163 #5 0x00007fc9e5236cc6 in native_fd_select (n=<optimized out>, readfds=<optimized out>, writefds=<optimized out>, exceptfds=<optimized out>, timeout=<optimized out>, th=<optimized out>) at /usr/src/debug/ruby-3.4.2/thread_pthread.c:2380 #6 do_select (p=p@entry=140504668626880) at /usr/src/debug/ruby-3.4.2/thread.c:4314 #7 0x00007fc9e50e7416 in rb_ensure (b_proc=0x7fc9e52368b0 <do_select>, data1=140504668626880, e_proc=0x7fc9e5232440 <select_set_free>, data2=140504668626880) at /usr/src/debug/ruby-3.4.2/eval.c:1074 #8 0x00007fc9e523700f in rb_thread_fd_select (max=max@entry=21, read=read@entry=0x7fc9cadce430, write=write@entry=0x7fc9cadce440, except=except@entry=0x0, timeout=timeout@entry=0x0) at /usr/src/debug/ruby-3.4.2/thread.c:4374 #9 0x00007fc9c97b5050 in init_fast_fallback_inetsock_internal (v=v@entry=140504668627872) at /usr/src/debug/ruby-3.4.2/ext/socket/ipsocket.c:894 #10 0x00007fc9e50e7416 in rb_ensure ( b_proc=b_proc@entry=0x7fc9c97b4950 <init_fast_fallback_inetsock_internal>, data1=data1@entry=140504668627872, e_proc=e_proc@entry=0x7fc9c97b7880 <fast_fallback_inetsock_cleanup>, data2=data2@entry=140504668627872) at /usr/src/debug/ruby-3.4.2/eval.c:1074 #11 0x00007fc9c97b7f3c in rsock_init_inetsock (self=self@entry=140504646018560, remote_host=remote_host@entry=140504646018640, remote_serv=remote_serv@entry=24691, local_host=local_host@entry=4, local_serv=local_serv@entry=4, type=type@entry=0, resolv_timeout=<optimized out>, connect_timeout=<optimized out>, fast_fallback=<optimized out>, test_mode_settings=<optimized out>) at /usr/src/debug/ruby-3.4.2/ext/socket/ipsocket.c:1285 #12 0x00007fc9c97b8216 in tcp_init (argc=<optimized out>, argv=<optimized out>, sock=140504646018560) at /usr/src/debug/ruby-3.4.2/ext/socket/tcpsocket.c:76 ``` `tcp_init` is the TCPSocket#initialize defined in tcpsocket.c, which just calls into the pure-C stack without ever backing out to check io_wait as is done in other socket-creation code path. It looks like the main difference is that init_fast_fallback_inetsock_internal hasn't been updated to be Fiber-aware (eg. init_inetsock_internal calls `rsock_connect` which uses the Fiber-aware `wait_connectable`), but `init_fast_fallback_inetsock_internal` is hard-coded to use thread stuff. In case anybody stumbles across this wondering why `Net::HTTP` sometimes blocks the Fiber scheduler during connect(), here's a quick workaround by hacking default `fast_fallback: false` into `TCPSocket.open`: ``` ruby orig_open = TCPSocket.method(:open) TCPSocket.define_singleton_method(:open) do |*args, **kwargs, &block| kwargs[:fast_fallback] ||= false orig_open.call(*args, **kwargs, &block) end ``` A slightly fancier workaround would be to have TCPSocket#initialize default `fast_fallback` to false if the current scheduler is non-nil. That would get rid of unexpected scheduler blocking without requiring a rewrite of the fast fallback code to be fiber-aware. I'm not sure if that's as trivial to implement in a c-defined method as it is in a native Ruby definition. -- https://bugs.ruby-lang.org/

2 2

[ruby-core:121507] [Ruby Bug#21212] IO::Buffer can be freed while its slice is locked
by hanazuki (Kasumi Hanazuki) 16 Apr '25

16 Apr '25

Issue #21212 has been reported by hanazuki (Kasumi Hanazuki). ---------------------------------------- Bug #21212: IO::Buffer can be freed while its slice is locked https://bugs.ruby-lang.org/issues/21212 * Author: hanazuki (Kasumi Hanazuki) * Status: Open * ruby -v: ruby 3.5.0dev (2025-04-01T16:11:01Z master 30e5e7c005) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ```ruby buffer = IO::Buffer.new(100) slice = buffer.slice buffer.locked do buffer.free rescue p $! #=> IO::Buffer::LockedError (expected) end slice.locked do p slice.locked? #=> true (expected) p buffer.locked? #=> false (what should this be?) slice.free rescue p $! #=> IO::Buffer::LockedError (expected) buffer.free # Should we allow this? slice.set_value(:U8, 0, 42) # raises IO::Buffer::InvalidatedError (surprising!) end ``` -- https://bugs.ruby-lang.org/

2 2

[ruby-core:121540] [Ruby Feature#21216] Implement Set as a core class
by jeremyevans0 (Jeremy Evans) 15 Apr '25

15 Apr '25

Issue #21216 has been reported by jeremyevans0 (Jeremy Evans). ---------------------------------------- Feature #21216: Implement Set as a core class https://bugs.ruby-lang.org/issues/21216 * Author: jeremyevans0 (Jeremy Evans) * Status: Open ---------------------------------------- I propose to implement Set as a core class. Set has been an autoloaded standard library since Ruby 3.2. The standard library Set is less efficient than it could be, as it uses Hash for storage, which stores unnecessary values for each item in the set. I've submitted a pull request that implements Set as a core class: https://github.com/ruby/ruby/pull/13074 Implementation details for the pull request: * Core Set uses a modified version of `st_table`, named `set_table`. Other than `s/st_/set_/`, the main difference is that the stored records do not have values, making them 1/3 smaller. `st_table_entry` stores `hash`, `key`, and `record` (value), while `set_table_entry` only stores `hash` and `key`. This results in large sets using ~33% less memory compared to stdlib Set. For small sets, core Set uses 20% less memory (160 bytes, while stdlib set uses 40 for Set and 160 for Hash). * All methods are implemented as cfuncs, except the pretty_print methods, which were moved to `lib/pp.rb` (which is where the pretty_print methods for other core classes are defined). As is typical for core classes, internal calls call C functions and not Ruby methods. For example, to check if something is a Set, `rb_obj_is_kind_of` is used, instead of calling `is_a?(Set)` on the related object. * Almost all methods use the same algorithm that the pure-Ruby implementation used. The exception is when calling `Set#divide` with a block with 2-arity. stdlib Set used a lazy-loaded tsort to implement this. I developed an algorithm that only allocates a single intermediate hash and does not need tsort. * The `flatten_merge` protected method is no longer necessary, so it is not implemented (it could be). * Similar to Hash/Array, subclasses of Set are no longer reflected in `inspect` output. * Documentation from stdlib Set was moved to core Set, with minor updates. I developed a comprehensive benchmark suite for all public Set methods (results attached). As you would expect, core Set is faster than stdlib Set in the majority of cases (90%), and multiple times faster in many cases (47% of cases are at least 2x faster, 31% of cases are at least 4x faster). There are a few cases where it is significantly slower: * `Set.new` with no arguments (~1.6x) * `Set#compare_by_identity` for small sets (~1.3x) * `Set#clone` for small sets (~1.5x) * `Set#dup` for small sets (~1.7x) Some of these are slower as Set does not currently use the AR table optimization that Hash does, so a new set_table is initialized for each Set. I'm not sure it's worth the complexity to have an AR table-like optimization for small sets (for hashes it makes sense, as small hashes are used everywhere in Ruby). The rbs and repl_type_completor bundled gems will need updates to support core Set. The pull request marks them as allowed failures. This passes all set tests with no changes. The following specs needed modification: * Modifying frozen set error message (changed for the better) * `Set#divide` when passed a 2-arity block no longer yields the same object as both the first and second argument (this seems like an issue with the previous implementation). * Set-like objects that override `is_a?` such that `is_a?(Set)` return `true` are no longer treated as Set instances. * `Set.allocate.hash` is no longer the same as `nil.hash` * `Set#join` no longer calls `Set#to_a` (it calls the underlying C function). * `Set#flatten_merge` protected method is not implemented. Previously, `set.rb` added a `SortedSet` autoload, which loads `set/sorted_set.rb`. This replaces the `Set` autoload in `prelude.rb` with a `SortedSet` autoload, but I recommend removing it and `set/sorted_set.rb` before the release of Ruby 3.5. This moves `test/set/test_set.rb` to `test/ruby/test_set.rb`, reflecting that switch to a core class. This does not move the spec files, as I'm not sure how they should be handled currently. Eventually, the set spec files should be moved to `spec/ruby/core`, but maybe not until Ruby 3.4 is no longer supported. This does not add any functions to the C-API (all functions in `set.c` are static). I think such functions can be added later as we find other places in core where it makes sense to use a Set instead of a Hash or Array, or as we get requests from extension authors. This is partially inspired by changes in Python 2.4 (released in November 2004), which changed the set implementation from a standard library class backed by a hash (dict in Python terms) to having it as a core class. ---Files-------------------------------- set-benchmark-output.txt (74.9 KB) -- https://bugs.ruby-lang.org/

2 1