Bug #21703: RUBY_CRASH_REPORT does not work when shelling out in some cases

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 3.2: DONTNEED, 3.3: REQUIRED, 3.4: DONE

[peterzhu2118 (Peter Zhu)]

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:

#!/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

[peterzhu2118 (Peter Zhu)]

• Status changed from Open to Closed

Applied in changeset git|190b017fc6c21ff7b61c2b5ece0294785e4a4ca2.

---

Don't use non blocking pipes for RUBY_CRASH_REPORT

[Bug #21703]

RUBY_CRASH_REPORT does not work in some cases when shelling out on Linux.
For example, given the following shell script dump.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

[k0kubun (Takashi Kokubun)]

• Backport changed from 3.2: DONTNEED, 3.3: REQUIRED, 3.4: REQUIRED to 3.2: DONTNEED, 3.3: REQUIRED, 3.4: DONE

ruby_3_4 a2ba1478e8c6a810c0fa08695a48f95ef5c29c45 merged revision(s) 190b017fc6c21ff7b61c2b5ece0294785e4a4ca2.