Issue #21703 has been updated by hsbt (Hiroshi SHIBATA). Backport changed from 3.2: DONTNEED, 3.3: DONE, 3.4: DONE to 3.2: DONTNEED, 3.3: REQUIRED, 3.4: DONE Unfortunately, [83637aea6ea726f7fc4c17e56ac60c289e2d98db](https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/836...) is failure with Linux platform. https://github.com/ruby/ruby/actions/runs/23475240114/job/68306538815 I reverted that for `ruby_3_3` branch. ---------------------------------------- Bug #21703: RUBY_CRASH_REPORT does not work when shelling out in some cases https://bugs.ruby-lang.org/issues/21703#change-116827 * Author: peterzhu2118 (Peter Zhu) * Status: Closed * Backport: 3.2: DONTNEED, 3.3: REQUIRED, 3.4: DONE ---------------------------------------- GitHub PR: https://github.com/ruby/ruby/pull/15292 RUBY_CRASH_REPORT does not work in some cases when shelling out on Linux. For example, given the following shell script dump.sh: ```sh #!/usr/bin/env bash cat > /tmp/crash ``` And we see it fails like this: ``` $ RUBY_CRASH_REPORT="|dump.sh" ruby -rfiddle -e "Fiddle::Pointer.new(1, 10)[0]" cat: -: Resource temporarily unavailable ``` -- https://bugs.ruby-lang.org/