Ruby Issue Tracking System

04/28/2019

04:04 PM Ruby Bug #15808 (Rejected): Forwardable doesn't allow forwarding the 'print' message

The following program forwards two messages to `@foo`: message 'print' and message 'bar'.
When I forward the 'print' message, I see a warning and the return value of `print` is always `nil`
(despite the fact that I specified my own ret... kyrylo (Kyrylo Silin)

08/09/2015

01:00 PM Ruby Feature #10211: Implement Signal.current_trap(sig)

I think we can close this. Thanks everyone for help! I finally figured out how to do that without modifying Ruby.
I updated https://github.com/kyrylo/multitrap kyrylo (Kyrylo Silin)

06/08/2015

04:24 AM Ruby Bug #11232: rb_compile_string from parse.y segfaults

Thanks for the tip!
I managed to fix the segfault with the following code:
https://github.com/kyrylo/fast_method_source/blob/d05a19993cccade40176c5f10b9008d79d2fc1e5/ext/fast_method_source/fast_method_source.c#L84-L85
I changed th... kyrylo (Kyrylo Silin)

06/07/2015

03:19 AM Ruby Bug #11232: rb_compile_string from parse.y segfaults

Nobuyoshi Nakada wrote:
> Is `vparser` in `parser_compile_string()` GCed?
It looks like so. I'm not sure how to verify that exactly,
but when I disable the GC, it doesn't segfault anymore.
I have added a second example, with `GC.... kyrylo (Kyrylo Silin)

01:23 AM Ruby Bug #11232 (Closed): rb_compile_string from parse.y segfaults

I'm using `rb_compile_string` in my project and invoke it in a loop.
Unfortunately, it segfaults for me.
I've set up a repository with a minimum reproducible case:
https://github.com/kyrylo/rb_compile_string_bug
The bug can be ob... kyrylo (Kyrylo Silin)

05/19/2015

12:59 AM Ruby Bug #11159: RubyVM::InstructionSequence.compile(nil) #=> segfault

Symbols also cause segfaults
~~~ruby
RubyVM::InstructionSequence.compile(:foo)
~~~
kyrylo (Kyrylo Silin)

05/17/2015

09:14 PM Ruby Bug #11159 (Closed): RubyVM::InstructionSequence.compile(nil) #=> segfault

The following code causes a segfault both for Ruby 2.2.2 and Ruby 2.2.0 (I haven't tested other versions).
The trace is attached.
~~~ruby
RubyVM::InstructionSequence.compile(nil)
~~~ kyrylo (Kyrylo Silin)

09/08/2014

06:18 PM Ruby Feature #10211: Implement Signal.current_trap(sig)

David Rodríguez wrote:
> Disregard my previous message, I thought all traps were executed from last to first, but only last one is. I guess that's why you're implementing Multitrap, right Kyrylo?
Exactly :) kyrylo (Kyrylo Silin)

04:54 PM Ruby Feature #10211: Implement Signal.current_trap(sig)

Nobuyoshi Nakada wrote:
> I can't get your point.
> ...
I want to get the trap defined by RSpec (and probably other gems loaded
before Multitrap that define various `trap` callbacks for other signals).
If I define a new `trap('INT'... kyrylo (Kyrylo Silin)

04:57 AM Ruby Feature #10211: Implement Signal.current_trap(sig)

Well, even monkey-patching won't help. kyrylo (Kyrylo Silin)