Unfortunately, ruby_options(0, 0) causes a SEGV in 1.9.3p327. The crash has been fixed ([Bug #7423]), but I don't think that ruby_options(0, 0) works correctly. It causes the embedded Ruby interpreter to read from standard input (the same as if you just typed "ruby" at a command prompt). I agree that ruby_options(0, 0) would be an acceptable alternative if it worked.