Project

General

Profile

Actions
Copy link

Bug #19891

open

rb_mRubyVMFrozenCore is reported by DTrace but ignored by TracePoint

Added by vo.x (Vit Ondruch) about 1 year ago. Updated about 1 year ago.

Status:
Open
Assignee:
-
Target version:
-
ruby -v:
ruby 3.3.0dev (2023-09-05 master 7c8932365f) [x86_64-linux]
Backport:
3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
[ruby-core:114814]

Description

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 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 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.

Actions
Copy link

Also available in: Atom PDF

Like0
Like0