From: "jhawthorn (John Hawthorn)" <noreply@...>
Date: 2022-01-31T20:45:46+00:00
Subject: [ruby-core:107403] [Ruby master Bug#18562] throw_data passed to rescue through require

Issue #18562 has been reported by jhawthorn (John Hawthorn).

----------------------------------------
Bug #18562: throw_data passed to rescue through require
https://bugs.ruby-lang.org/issues/18562

* Author: jhawthorn (John Hawthorn)
* Status: Open
* Priority: Normal
* Assignee: jhawthorn (John Hawthorn)
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
When we throw in a require it's incorrectly considered as a raise, making the `T_IMEMO` `throw_data` object accessible via rescue (in a contrived case). In regular usage this is unlikely to cause an issue because `Module#===` immediately returns false for objects with klass == 0.

With `test_throw.rb`:
```
throw :extdep, 42
```

and 

```
class Anything < Exception
  def self.===(_); true; end
end

catch(:extdep) do
  begin
    require "./test_throw"
  rescue Anything => e
    p e
  end
end
```

We get

```
in 'p': method inspect' called on unexpected T_IMEMO object (0x00007f5e1486b130 flags=0x10000301a) (NotImplementedError)
```

I've proposed a fix via PR https://github.com/ruby/ruby/pull/5513



-- 
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>