From: "nagachika (Tomoyuki Chikanaga) via ruby-core" <ruby-core@...>
Date: 2023-08-12T04:54:48+00:00
Subject: [ruby-core:114385] [Ruby master Bug#19833] Superclass of BasicObject is broken.

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

Backport changed from 3.0: DONTNEED, 3.1: DONTNEED, 3.2: REQUIRED to 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONE

ruby_3_2 b11f238a811513b31c4f65c822370ac470f438dc merged revision(s) 72d1a790cfe0e4a457db98c587f1acaa5e39f001.

----------------------------------------
Bug #19833: Superclass of BasicObject is broken.
https://bugs.ruby-lang.org/issues/19833#change-104133

* Author: ksss (Yuki Kurihara)
* Status: Closed
* Priority: Normal
* ruby -v: ruby 3.3.0dev (2023-08-08T00:21:45Z master 69292676a2) [arm64-darwin22]
* Backport: 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONE
----------------------------------------
I encountered a phenomenon where a non-class object appeared in the superclass of BasicObject.

The minimum reproduction code is below.

```rb
module Mod
end

BasicObject.include Mod
# or BasicObject.prepend Mod

p BasicObject.superclass
#=> 2431129 or false
```

I think it is a practical problem because I found it by running code that monitors `singleton_method_added` as follows.

https://github.com/ksss/orthoses/blob/341019c78ba625bc5d36c0f359c7d88621990f78/lib/orthoses/lazy_trace_point.rb#L35-L48



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/