[Rubyinstaller-devel] exec bug in RC2

Luis Lavena luislavena at gmail.com
Thu Dec 18 21:33:32 EST 2008

On Thu, Dec 18, 2008 at 9:41 AM, Zakaria <z4k4ri4 at gmail.com> wrote:
> Hi,
> I'm testing the RC2 and find this bug while trying to run rails script/dbconsole
> E:\>ruby -v
> ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]
> E:\>ruby -e 'exec "notepad.exe", "test.txt"'
> -e:1:in `exec': No such file or directory - notepad.exe (Errno::ENOENT)
>        from -e:1
> E:\>ruby -e 'exec "notepad", "test.txt"'
> E:\>ruby -e 'exec "notepad.exe"'
> Note there is an error when I do exec 'notepad.exe', 'test.txt'
> Compare with the ruby in InstantRails 2.0:
> C:\rails2\rails_apps>ruby -v
> ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]
> C:\rails2\rails_apps>ruby -e 'exec "notepad.exe", "test.txt"'
> C:\rails2\rails_apps>ruby -e 'exec "notepad", "test.txt"'
> C:\rails2\rails_apps>ruby -e 'exec "notepad.exe"'
> There is no such error. A regression perhaps?
> Wassallam,

Hello Zakaria.

both exec() and system() calls are broken on Windows, mostly all the
multiple arguments calls changed behavior from patchlevel 111 to 287.

There is a discussion about that on ruby-core:


This is pure ruby problem, and currently we are bound to the binary
releases officially made.

I cannot suggest more than raise this issue to Ruby redmine, and hope
you get heard.


Luis Lavena
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

More information about the Rubyinstaller-devel mailing list