[#81492] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — normalperson@...
Issue #13618 has been reported by normalperson (Eric Wong).
12 messages
2017/06/01
[#88695] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/08/27
> https://bugs.ruby-lang.org/issues/13618
[#81569] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
3 messages
2017/06/04
[#81581] [Ruby trunk Bug#13632] Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread. — sir.nickolas@...
Issue #13632 has been reported by nvashchenko (Nikolay Vashchenko).
4 messages
2017/06/05
[#81590] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures. — Eric Wong <normalperson@...>
ko1@ruby-lang.org wrote:
5 messages
2017/06/06
[#81591] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81596] Re: [ruby-cvs:66203] Re: Re: ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81825] [Ruby trunk Feature#13697] [PATCH]: futex based thread primitives — normalperson@...
Issue #13697 has been reported by normalperson (Eric Wong).
3 messages
2017/06/29
[ruby-core:81607] [Ruby trunk Bug#13324][Open] IRB Segmentation Fault from eval infinite loop
From:
srodman7689@...
Date:
2017-06-07 14:18:44 UTC
List:
ruby-core #81607
Issue #13324 has been updated by srodman7689@gmail.com (Sean Rodman). Status changed from Closed to Open The issues is not the stack overflow but the segmentation fault I described when running the same code in the above listed irb version. ---------------------------------------- Bug #13324: IRB Segmentation Fault from eval infinite loop https://bugs.ruby-lang.org/issues/13324#change-65305 * Author: srodman7689@gmail.com (Sean Rodman) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- I am not sure if this has already been taken care of or not but I am using ruby 2.3.0 and irb 0.9.6(09/06/30) and when I run the below code I get a segmentation fault ```ruby a = "eval a"; eval a ``` when running the same code with just the ruby interpreter I get the below error which is what I would expect ``` -e:1:in `eval': stack level too deep (SystemStackError) from (eval):1:in `<main>' from (eval):1:in `eval' from (eval):1:in `<main>' from (eval):1:in `eval' from (eval):1:in `<main>' from (eval):1:in `eval' from (eval):1:in `<main>' from (eval):1:in `eval' ... 9507 levels... from (eval):1:in `eval' from (eval):1:in `<main>' from -e:1:in `eval' from -e:1:in `<main>' ``` -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>