Bug #10563: system() call hangs if command is too long

• Status: Closed
• Assignee: windows
• Target version: 2.2.0
• ruby -v: ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]
• Backport: 2.0.0: DONTNEED, 2.1: DONE

[Maturin (Lars Benner)]

In some situations another process, which was started using Kernel::system(), hangs right from the beginning, i.e. the process was started but nothing is actually executed.

On my system this happened, when the single command string passed to system call exceeded 1022 characters.

A very interesting fact is, that this only happens, if the command at the beginning is given with '/' in the path. After I replaced the '/' with '', everything is working fine.

Please find attached two scripts for reproducing this issue. Just call 'ruby caller.rb' and observe that everything hangs after the command line got to long. After changing the Ruby interpreter in the file. everything works as expected.

[Maturin (Lars Benner)]

Actually I found this problem, while using rake and I raised another bug for rake first. Perhaps it contains some useful information.

https://github.com/ruby/rake/issues/5

[usa (Usaku NAKAMURA)]

• Category changed from platform/mingw to platform/windows
• Status changed from Open to Assigned
• Assignee changed from nobu (Nobuyoshi Nakada) to windows

Thank you for reporting!
We'll fix it.

memo: This is a bug of w32_spawn().

[usa (Usaku NAKAMURA)]

• Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN to 2.0.0: DONTNEED, 2.1: REQUIRED

[usa (Usaku NAKAMURA)]

• Status changed from Assigned to Closed

fixed at r48690.

[nagachika (Tomoyuki Chikanaga)]

• Backport changed from 2.0.0: DONTNEED, 2.1: REQUIRED to 2.0.0: DONTNEED, 2.1: DONE

Backported into ruby_2_1 branch at r49997.