[ruby-core:66648] [ruby-trunk - Bug #10563] [Open] system() call hangs if command is too long

[ruby-core:66648] [ruby-trunk - Bug #10563] [Open] system() call hangs if command is too long

[lars.benner]

Issue #10563 has been reported by Lars Benner.

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

* Author: Lars Benner
* Status: Open
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* Category: platform/mingw
* Target version: current: 2.2.0
* ruby -v: ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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--------------------------------
callee.rb (283 Bytes)
caller.rb (797 Bytes)


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

[ruby-core:66649] [ruby-trunk - Bug #10563] system() call hangs if command is too long

[lars.benner]

Issue #10563 has been updated by 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

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

* Author: Lars Benner
* Status: Open
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* Category: platform/mingw
* Target version: current: 2.2.0
* ruby -v: ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:66650] [ruby-trunk - Bug #10563] [Assigned] system() call hangs if command is too long

[usa]

Issue #10563 has been updated by Usaku NAKAMURA.

Category changed from platform/mingw to platform/windows
Status changed from Open to Assigned
Assignee changed from Nobuyoshi Nakada to cruby-windows

Thank you for reporting!
We'll fix it.

memo: This is a bug of w32_spawn().

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

* 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: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:66652] [ruby-trunk - Bug #10563] system() call hangs if command is too long

[usa]

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/

[ruby-core:66653] [ruby-trunk - Bug #10563] [Closed] system() call hangs if command is too long

[usa]

Issue #10563 has been updated by Usaku NAKAMURA.

Status changed from Assigned to Closed

fixed at r48690.

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

* Author: Lars Benner
* Status: Closed
* 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/

[ruby-core:68548] [Ruby trunk - Bug #10563] system() call hangs if command is too long

[nagachika00]

Issue #10563 has been updated by 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.

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

* Author: Lars Benner
* Status: Closed
* Priority: Normal
* Assignee: cruby-windows
* ruby -v: ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]
* Backport: 2.0.0: DONTNEED, 2.1: DONE
----------------------------------------
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/