Actions
Bug #21992
closedDefining BasicObject#initialize causes segmentation fault
Bug #21992:
Defining BasicObject#initialize causes segmentation fault
Description
Simplest reproduction:
class BasicObject
def initialize
end
end
In Ruby HEAD, 4.0.2, 3.4.7, and 3.3.11 on macOS, this leads to an immediate segmentation fault. I also got this on Ruby 3.4.1 on Linux.
What I would expect, a warning similar to that raised if you do the same on Object.
I couldn't find a previous mention of this. It's not something you would ever write yourself, but I guess it could arise during metaprogramming or dynamic code generation with the right (wrong) constant name in play.
Actions