[#101179] Spectre Mitigations — Amel <amel.smajic@...>
Hi there!
5 messages
2020/12/01
[#101180] Re: Spectre Mitigations
— Chris Seaton <chris@...>
2020/12/01
I wouldn’t recommend using Ruby to run in-process untrusted code in the first place. Are people doing that?
[#101694] Ruby 3.0.0 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 3.0.0. From 2015 we
4 messages
2020/12/25
[ruby-core:101623] [Ruby master Bug#17408] Fiber.backtrace returns [] when unavailable, unlike Thread
From:
marcandre-ruby-core@...
Date:
2020-12-22 05:09:29 UTC
List:
ruby-core #101623
Issue #17408 has been updated by marcandre (Marc-Andre Lafortune).
ioquatix (Samuel Williams) wrote in #note-3:
> > should be nil
>
> when the fiber is dead.
Right. Doc does call `resume` but not this issue. Correct code should read:
```ruby
f = Fiber.new{}
f.resume
f.backtrace # => currently [] (should be nil)
```
----------------------------------------
Bug #17408: Fiber.backtrace returns [] when unavailable, unlike Thread
https://bugs.ruby-lang.org/issues/17408#change-89413
* Author: zverok (Victor Shepelev)
* Status: Closed
* Priority: Normal
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
```ruby
t = Thread.new{}
p t.backtrace
# => nil
f = Fiber.new{}
p f.backtrace
# => []
```
It seems inconsistent, is this intentional?
Ping @ioquatix
--
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>