[ruby-core:98187] [Ruby master Bug#16834] rb_profile_frame_classpath only recognize class singleton methods, not module singleton methods

< ^ > P N |<>| ^ _>< --- | ~ ...Help

Issue #16834 has been updated by tenderlovemaking (Aaron Patterson).

Backport changed from 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN to 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED

I've merged this in cbe4f75ef802f13d05f94e42274b65a062bd3666.  It's been a bug for a while so I'm going to mark back port for 2.5, 2.6, and 2.7.  ¡é

----------------------------------------
Bug #16834: rb_profile_frame_classpath only recognize class singleton methods, not module singleton methods
https://bugs.ruby-lang.org/issues/16834#change-85427

* Author: byroot (Jean Boussier)
* Status: Open
* 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: REQUIRED
----------------------------------------
Proposed patch: https://github.com/ruby/ruby/pull/3084

Right now `SomeClass.method` is properly named, but `SomeModule.method`
is displayed as `#<Module:0x000055eb5d95adc8>.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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>