Issue #20501 has been updated by nobu (Nobuyoshi Nakada). luke-gru (Luke Gruber) wrote in #note-5:
For example, this is a minimal reproduction:
I can't reproduce it with master. ```ruby def my_method ivar = nil # seems to be needed to reproduce the issue if false && defined? File::TMPFILE end raise "woops" end my_method ``` ```shell-session $ ./bin/ruby -v bug-20501.rb ruby 3.4.0dev (2024-09-06T00:32:47Z master 81b74c9fad) [aarch64-linux] bug-20501.rb:2: warning: assigned but unused variable - ivar bug-20501.rb:5:in 'Object#my_method': woops (RuntimeError) from bug-20501.rb:7:in '<main>' ``` ```shell-session $ ./ruby -v bug-20501.rb ruby 3.4.0dev (2024-09-06T00:32:47Z master 81b74c9fad) [arm64-darwin23] bug-20501.rb:2: warning: assigned but unused variable - ivar bug-20501.rb:5:in 'Object#my_method': woops (RuntimeError) from bug-20501.rb:7:in '<main>' ``` ---------------------------------------- Bug #20501: ruby SEGV https://bugs.ruby-lang.org/issues/20501#change-109660 * Author: akr (Akira Tanaka) * Status: Assigned * Assignee: tenderlovemaking (Aaron Patterson) * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I encountered SEGV of ruby. ``` % ./ruby -v ruby 3.4.0dev (2024-05-22T06:59:19Z master 5613d6e95b) [x86_64-linux] % ./ruby t.rb t.rb:33: [BUG] Segmentation fault at 0x00007fc243696098 ruby 3.4.0dev (2024-05-22T06:59:19Z master 5613d6e95b) [x86_64-linux] -- Control frame information ----------------------------------------------- c:0003 p:0000 s:4294967313 e:000018 METHOD t.rb:33 c:0002 p:0022 s:0006 e:000005 EVAL t.rb:52 [FINISH] c:0001 p:0000 s:0003 E:000350 DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- t.rb:52:in '<main>' t.rb:33:in 'create_no_file' -- Threading information --------------------------------------------------- Total ractor count: 1 Ruby thread count for this ractor: 1 -- Machine register context ------------------------------------------------ RIP: 0x000055a1cdc8bb9c RBP: 0x000055a1cee844b0 RSP: 0x00007ffcde5cdae0 RAX: 0x00007fc2436960a0 RBX: 0x00007fba43795f68 RCX: 0x0000000000000000 RDX: 0x000055a1cf115cf0 RDI: 0x0000000000000009 RSI: 0x00007fba28526860 R8: 0x00007fba436960a1 R9: 0x0000000000000000 R10: 0x00007fba28526860 R11: 0x0000000000000003 R12: 0x0000000000000006 R13: 0x00007fba2853b698 R14: 0x0000000d00000009 R15: 0x0000000000000b21 EFL: 0x0000000000010246 -- C level backtrace information ------------------------------------------- /home/ruby/t2/ruby/ruby(rb_print_backtrace+0x14) [0x55a1cdcae243] /home/ruby/t2/ruby/vm_dump.c:820 /home/ruby/t2/ruby/ruby(rb_vm_bugreport) /home/ruby/t2/ruby/vm_dump.c:1151 /home/ruby/t2/ruby/ruby(rb_bug_for_fatal_signal+0xf8) [0x55a1cde5abe8] /home/ruby/t2/ruby/error.c:1108 /home/ruby/t2/ruby/ruby(sigsegv+0x44) [0x55a1cdbf7864] /home/ruby/t2/ruby/signal.c:929 /lib/x86_64-linux-gnu/libc.so.6(0x7fba438f8050) [0x7fba438f8050] /home/ruby/t2/ruby/ruby(vm_exec_handle_exception+0x2ac) [0x55a1cdc8bb9c] /home/ruby/t2/ruby/vm.c:2782 ... ``` `t.rb` and the full crash report are attached. ---Files-------------------------------- t.rb (1.27 KB) crash.txt (15.8 KB) crash2.txt (11.2 KB) -- https://bugs.ruby-lang.org/