From: Eric Wong <normalperson@...>
Date: 2017-09-23T04:23:32+00:00
Subject: [ruby-core:82940] Re: [Ruby trunk Bug#13887] test/ruby/test_io.rb may get stuck with FIBER_USE_NATIVE=0 on Linux

s.wanabe@gmail.com wrote:
> I guess `cont->machine.stack_src` should not contain the under thread_start_func_1() stack.
> Because this area will be used and overwritten by pthread, especially stack_list_{add,del} in nptl/allocatestack.c.
> If cont_restore_1() copies `cont->machine.stack` to `cont->machine.stack_src`, it may be reverted above changes and corrupted stack_cache list structures.

I think this makes your patch necessary for callcc use
regardless of FIBER_USE_NATIVE value.

Shall I commit [ruby-core:82925]?

My Thriber patch has a different problem with FIBER_USE_NATIVE=0
and I need to use heap alloccation for platforms without native fiber.

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>