Building Ruby 2.4.0-preview1 fails on Centos 5 with the error below. I know that this is an ancient version, but... Graham % gcc -v Using built-in specs. Target: i386-redhat-linux Configured with: ../configure --prefix=/usr --ma...gfim (Graham Menhennitt)
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 sam...gfim (Graham Menhennitt)
The documented way to embed a Ruby interpreter is to call: RUBY_INIT_STACK; ruby_init(); ruby_init_loadpath(); However, this leaves the Ruby environment incomplete. As an example, the following program: #include <r...gfim (Graham Menhennitt)
In ruby_process_options(), there is a line: ruby_script(argv[0]); /* for the time being */ This dereferences argv whether argc is zero or not. This causes a SEGV if there are no command line args. It should be changed to somet...gfim (Graham Menhennitt)
=begin I'm getting an occasional crash when calling the += operator for a String. It happens fairly rarely (maybe once per 10,000 calls), but it always looks the same.