Bug #7239: Can't read from subprocess when run with rubyw on windows

• Status: Closed
• Assignee: usa (Usaku NAKAMURA)
• Target version: -
• ruby -v: ruby 1.9.3p194 (2012-04-20) [i386-mingw32]

[mthiede (Martin Thiede)]

File.open 'res.txt', 'w' do |f|
f << dir
end

when run with "rubyw", the file "res.txt" will be empty, when run with "ruby" it will contain the output of the "dir" command

the problem is present in Ruby versions 1.9.1, 1.9.2 and 1.9.3
the problem is not present in Ruby version 1.8.7

[mthiede (Martin Thiede)]

I tested this with Windows 7

[luislavena (Luis Lavena)]

• Description updated (diff)
• Category set to core
• Status changed from Open to Assigned
• Assignee set to usa (Usaku NAKAMURA)

[usa (Usaku NAKAMURA)]

• Status changed from Assigned to Closed
• % Done changed from 0 to 100

This issue was solved with changeset r37388.
Martin, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

---

• process.c (redirect_dup2): set standard handles when new fd is stdio,
  because if there is no allocated console at the moment Windows does
  not automatically associate it for child process's standard handle.
  this is adhoc workaround.
  reported by Martin Thiede at [ruby-core:48542] [Bug #7239].

• io.c (rb_cloexec_dup2): ditto.

[ryanatball (Ryan Melton)]

Please backport this to Ruby 1.9.3.