From: "nagachika (Tomoyuki Chikanaga)" <noreply@...>
Date: 2022-03-13T06:43:08+00:00
Subject: [ruby-core:107872] [Ruby master Bug#18562] throw_data passed to rescue through require

Issue #18562 has been updated by nagachika (Tomoyuki Chikanaga).

Backport changed from 2.6: DONTNEED, 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONE to 2.6: DONTNEED, 2.7: REQUIRED, 3.0: DONE, 3.1: DONE

ruby_3_0 0bd3e436e27c048933133bc19f863c954ed3e3a6 merged revision(s) c79d2e54748f52c5023b0a1ee441561df9826c17.

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

* Author: jhawthorn (John Hawthorn)
* Status: Closed
* Priority: Normal
* Assignee: jhawthorn (John Hawthorn)
* Backport: 2.6: DONTNEED, 2.7: REQUIRED, 3.0: DONE, 3.1: DONE
----------------------------------------
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>