Code review comment for ~lucaskanashiro/ubuntu/+source/ruby3.1:fix-segfault

Hm, let me step back a little bit here...

I'm actually seeing the following dep8 failure against armhf:

1307s
1307s 1) Error:
1307s TestThread#test_signal_at_join:
1307s Timeout::Error: execution of assert_separately expired timeout (120 sec)
1307s pid 3076 exit 1
1307s |
1307s | -:27:in `gets': Exception raised: (Test::Unit::AssertionFailedError)
1307s | <#<SignalException: SIGTERM>>
1307s | Backtrace:
1307s | -:27:in `gets'
1307s | -:27:in `block (3 levels) in <main>'
1307s | -:21:in `times'
1307s | -:21:in `block (2 levels) in <main>'.
1307s | from -:27:in `block (3 levels) in <main>'
1307s | from -:21:in `times'
1307s | from -:21:in `block (2 levels) in <main>'
1307s | from /tmp/autopkgtest.54UrK0/autopkgtest_tmp/tool/lib/core_assertions.rb:176:in `assert_nothing_raised'
1307s | from -:20:in `block in <main>'
1307s | from -:10:in `popen'
1307s | from -:10:in `<main>'
1307s | -:27:in `gets': SIGTERM (SignalException)
1307s | from -:27:in `block (3 levels) in <main>'
1307s | from -:21:in `times'
1307s | from -:21:in `block (2 levels) in <main>'
1307s | from /tmp/autopkgtest.54UrK0/autopkgtest_tmp/tool/lib/core_assertions.rb:176:in `assert_nothing_raised'
1307s | from -:20:in `block in <main>'
1307s | from -:10:in `popen'
1307s | from -:10:in `<main>'
1307s
1307s /tmp/autopkgtest.54UrK0/autopkgtest_tmp/test/ruby/test_thread.rb:1390:in `test_signal_at_join'
1307s
1307s Finished tests in 1004.332484s, 17.1915 tests/s, 2691.3348 assertions/s.
1307s 17266 tests, 2702995 assertions, 0 failures, 1 errors, 37 skips
1307s
1307s ruby -v: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm-linux-gnueabihf]
1308s autopkgtest [19:42:56]: test run-all: -----------------------]
1321s autopkgtest [19:43:09]: test run-all: - - - - - - - - - - results - - - - - - - - - -
1321s run-all FAIL non-zero exit status 1

https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-lucaskanashiro-testing/mantic/armhf/r/ruby3.1/20240325_194808_a2f6a@/log.gz

I see that the ruby3.1 from the archive doesn't have this failure, so I'm wondering what's happening. Any ideas?