[ruby-core:114815] [Ruby master Bug#19891] rb_mRubyVMFrozenCore is reported by DTrace but ignored by TracePoint

Issue #19891 has been updated by ko1 (Koichi Sasada).


> `TODO: remove it`

I have a plan to remove `rb_mRubyVMFrozenCore` but not implemented yet.

Anyway, I don't have any objection to skip it on Dtrace too.

----------------------------------------
Bug #19891: rb_mRubyVMFrozenCore is reported by DTrace but ignored by TracePoint
https://bugs.ruby-lang.org/issues/19891#change-104661

* Author: vo.x (Vit Ondruch)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.3.0dev (2023-09-05 master 7c8932365f) [x86_64-linux]
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
This is related to #18257 where I wonder why rb_mRubyVMFrozenCore is ignored by TracePoint (if I am not mistaken) [1]:

~~~
        if (ec->trace_arg == NULL && /* check reentrant */
            trace_arg->self != rb_mRubyVMFrozenCore /* skip special methods. TODO: remove it. */) {
~~~

This was introduced in commit:git|1be7c799e6ed39f7ac41906c05db149e8c391add but hard to guess what was the reason. If there were issues similar to @18257 or if it is by design.

The `TODO` part was introduced by commit:git|4a4a702e61d1c5585d522f1185a82a5685c554f6 which also does not give a clue what is intention here.

Generally, my point is that it is strange that DTrace would report about rb_mRubyVMFrozenCore while TracePoint is happy to skip it.

[1]: https://github.com/ruby/ruby/blob/647390308239fbf82d159ecd83ed8df090af518d/vm_trace.c#L431




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