[#68478] Looking for MRI projects for Ruby Google Summer of Code 2015 — Tony Arcieri <bascule@...>
Hi ruby-core,
10 messages
2015/03/10
[#68480] Re: Looking for MRI projects for Ruby Google Summer of Code 2015
— SASADA Koichi <ko1@...>
2015/03/10
I have.
[#68549] Re: Looking for MRI projects for Ruby Google Summer of Code 2015
— SASADA Koichi <ko1@...>
2015/03/17
I sent several ideas on previous, mail, but they are seems rejected?
[#68493] [Ruby trunk - Feature #10532] [PATCH] accept_nonblock supports "exception: false" — nobu@...
Issue #10532 has been updated by Nobuyoshi Nakada.
5 messages
2015/03/11
[#68503] Re: [Ruby trunk - Feature #10532] [PATCH] accept_nonblock supports "exception: false"
— Eric Wong <normalperson@...>
2015/03/12
Committed as r49948.
[#68504] Re: [Ruby trunk - Feature #10532] [PATCH] accept_nonblock supports "exception: false"
— Nobuyoshi Nakada <nobu@...>
2015/03/12
On 2015/03/12 12:08, Eric Wong wrote:
[#68506] Seven stacks (and two questions) — Jakub Trzebiatowski <jaktrze1@...>
The Ruby Hacking Guide says that Ruby has窶ヲ seven stacks. Is it an implementation choice (and it could be implemented with one stack), or is there really a need for seven logical stacks? For example, Lua has one stack, and still closures with upvalues are totally possible (it窶冱 like Ruby窶冱 blocks that can reference local variables of their enclosing method, but it works for any function with any upvalues).
5 messages
2015/03/12
[#68520] Possible regression in 2.1 and 2.2 in binding when combined with delegate? — Joe Swatosh <joe.swatosh@...>
# The following code
3 messages
2015/03/14
[#68604] GSOC project Cross-thread Fiber support — surya pratap singh raghuvanshi <oshosurya@...>
- *hi i am a third year computer science student interested in working
6 messages
2015/03/22
[#68606] Re: GSOC project Cross-thread Fiber support
— Tony Arcieri <bascule@...>
2015/03/22
Hi Surya,
[#68619] Re: GSOC project Cross-thread Fiber support
— surya pratap singh raghuvanshi <oshosurya@...>
2015/03/23
hi tony,
[ruby-core:68434] [Ruby trunk - Bug #10847] SystemStackError after NameError prepends a module
From:
hanachin@...
Date:
2015-03-05 17:14:45 UTC
List:
ruby-core #68434
Issue #10847 has been updated by Seiei Higa.
How to reproduce:
1. prepend Module to the class
2. call the method that calls cfunc `rb_call_super`
The following code causes SystemStackError too, because `Float#numerator` calls `rb_call_super`.
```ruby
module M; end
Float.prepend M
0.3.numerator
```
I wrote a patch for this issue.
```diff
diff --git vm_eval.c vm_eval.c
index 6eeee5f..4039b6c 100644
--- vm_eval.c
+++ vm_eval.c
@@ -273,7 +273,8 @@ vm_call_super(rb_thread_t *th, int argc, const VALUE *argv)
rb_bug("vm_call_super: should not be reached");
}
- klass = RCLASS_SUPER(cfp->klass);
+ klass = RCLASS_ORIGIN(cfp->klass);
+ klass = RCLASS_SUPER(klass);
id = cfp->me->def->original_id;
me = rb_method_entry(klass, id, &klass);
if (!me) {
```
----------------------------------------
Bug #10847: SystemStackError after NameError prepends a module
https://bugs.ruby-lang.org/issues/10847#change-51780
* Author: Yuki Nishijima
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v: ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
The following code causes `SystemStackError`.
```ruby
module Foo
end
NameError.prepend Foo
foo rescue $!
```
And here is the full backtrace:
```
system_stack_error_from_name_error.rb:3:in `initialize': stack level too deep (SystemStackError)
from system_stack_error_from_name_error.rb:3:in `initialize'
from system_stack_error_from_name_error.rb:3:in `initialize'
from system_stack_error_from_name_error.rb:3:in `initialize'
from system_stack_error_from_name_error.rb:3:in `initialize'
from system_stack_error_from_name_error.rb:3:in `initialize'
from system_stack_error_from_name_error.rb:3:in `initialize'
from system_stack_error_from_name_error.rb:3:in `initialize'
from system_stack_error_from_name_error.rb:3:in `initialize'
... 10907 levels...
from system_stack_error_from_name_error.rb:3:in `initialize'
from system_stack_error_from_name_error.rb:3:in `initialize'
from system_stack_error_from_name_error.rb:3:in `method_missing'
from system_stack_error_from_name_error.rb:3:in `<main>'
```
This happens on Ruby 2.0.0, 2,1,5, 2.2.0 and ruby-trunk(rev 49451).
--
https://bugs.ruby-lang.org/