Project

General

Profile

Actions
Copy link

Bug #21694

closed

Crash when looking up super method from BasicObject

Bug #21694: Crash when looking up super method from BasicObject

Added by byroot (Jean Boussier) 22 days ago. Updated about 24 hours ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
Backport:
3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONE
[ruby-core:123835]

Description

Initially reported on Reddit by easydwh https://old.reddit.com/r/ruby/comments/1ozhupr/is_a_ruby_segmentation_fault_a_bug_if_you_are/

Repro:

class BasicObject
  def basic_call_no_super
    super
  end
end

"test".basic_call_no_super

Pull Request: https://github.com/ruby/ruby/pull/15221

Updated by byroot (Jean Boussier) 22 days ago Actions
Copy link
 #1

  • Description updated (diff)

Updated by byroot (Jean Boussier) 15 days ago Actions
Copy link
 #2

  • Status changed from Open to Closed

Applied in changeset git|a36ebb18a6d4c4726915b6d7c16cfdbf4e5d417b.

vm_cc_new: don't assume cme is present.

[Bug #21694]

vm_search_super_method explictly calls vm_cc_new with cme=NULL
when there is no super class.

Updated by k0kubun (Takashi Kokubun) 1 day ago Actions
Copy link
 #3 [ruby-core:124062]

Backporting this causes multiple conflicts. Could you file a backport PR to ruby_3_4 please?

Updated by byroot (Jean Boussier) about 24 hours ago Actions
Copy link
 #4 [ruby-core:124079]

  • Backport changed from 3.2: DONTNEED, 3.3: DONTNEED, 3.4: REQUIRED to 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONE
Actions
Copy link

Also available in: PDF Atom