From: usa@...
Date: 2014-12-03T02:18:50+00:00
Subject: [ruby-core:66652] [ruby-trunk - Bug #10563] system() call hangs if	command is too long

Issue #10563 has been updated by Usaku NAKAMURA.

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

----------------------------------------
Bug #10563: system() call hangs if command is too long
https://bugs.ruby-lang.org/issues/10563#change-50262

* Author: Lars Benner
* Status: Assigned
* Priority: Normal
* Assignee: cruby-windows
* Category: platform/windows
* Target version: current: 2.2.0
* ruby -v: ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]
* Backport: 2.0.0: DONTNEED, 2.1: REQUIRED
----------------------------------------
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. 






---Files--------------------------------
caller.rb (797 Bytes)
callee.rb (283 Bytes)


-- 
https://bugs.ruby-lang.org/