ruby-core

peter-rl@suschlik.de wrote:

nobu@ruby-lang.org wrote:

Was there any output in stderr from this test? Thanks.

normalperson@yhbt.net wrote:

normalperson@yhbt.net wrote:

normalperson@yhbt.net wrote:

Can you try a higher fd number instead of 3?

ngotogenome@gmail.com wrote:

ngotogenome@gmail.com wrote:

tenderlove@ruby-lang.org wrote:

On 2015/07/16 5:35, Bertram Scharpf wrote:

Hi again,

Sorry, but I think rb_divert_reserved_fd seems a racy fix. I think the

Alternative patch, but I relying on sched_yield() may be unreliable.

merch-redmine@jeremyevans.net wrote:

nobu@ruby-lang.org wrote:

ngotogenome@gmail.com wrote:

Looks like you sent a backwards patch. We will need to use -R with

OK, so I've decided ugly #freeze is better than broken compatibility

In fact, here's an utterly trivial repro:

richard.schneeman@gmail.com wrote:

Eric Wong <normalperson@yhbt.net> wrote:

Possible fix is to memoize hashval inside struct RSymbol:

Thanks for testing, committed as r51410 and 2.2 backport requested.

Since you're using SSLSocket, I recommend dumping a backtrace when you

Thanks for testing. A backporter will backport it to 2.2 since this

bar.hofesh@safe-t.com wrote:

Thanks, I'm taking a look.

log:

Possibly related: [Bug #11384] sometimes fails with uninitialized constant

ngotogenome@gmail.com wrote: