From: nagachika00@... Date: 2020-07-25T05:17:46+00:00 Subject: [ruby-core:99326] [Ruby master Bug#16834] rb_profile_frame_classpath only recognize class singleton methods, not module singleton methods Issue #16834 has been updated by nagachika (Tomoyuki Chikanaga). Backport changed from 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED to 2.5: REQUIRED, 2.6: REQUIRED, 2.7: DONE ruby_2_7 12391cdbe11f3fbeb3b04c30b944139e5bbd9ea6 merged revision(s) cbe4f75ef802f13d05f94e42274b65a062bd3666. ---------------------------------------- Bug #16834: rb_profile_frame_classpath only recognize class singleton methods, not module singleton methods https://bugs.ruby-lang.org/issues/16834#change-86721 * Author: byroot (Jean Boussier) * Status: Closed * Priority: Normal * ruby -v: ruby 2.5.5p157 ruby 2.6.6p146 ruby 2.8.0dev * Backport: 2.5: REQUIRED, 2.6: REQUIRED, 2.7: DONE ---------------------------------------- Proposed patch: https://github.com/ruby/ruby/pull/3084 Right now `SomeClass.method` is properly named, but `SomeModule.method` is displayed as `#.method` which makes profiling annoying. This particularly impact StackProf. it's a problem at least since Ruby 2.5, maybe older but there's not point backporting that far back. -- https://bugs.ruby-lang.org/ Unsubscribe: