From: richardboehme via ruby-core <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: richardboehme <noreply@ruby-lang.org>
Subject: [ruby-core:119272] [Ruby master Feature#20757] Make rb_tracearg_(parameters|eval_script|instruction_sequence) public C-API
Date: Fri, 20 Sep 2024 14:38:35 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-20757.20240920143834.53944@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20757.20240920143834.53944@ruby-lang.org>
Issue #20757 has been reported by richardboehme (Richard Böhme).
----------------------------------------
Feature #20757: Make rb_tracearg_(parameters|eval_script|instruction_sequence) public C-API
https://bugs.ruby-lang.org/issues/20757
* Author: richardboehme (Richard Böhme)
* Status: Open
----------------------------------------
**Abstract**
As a C-extension developer when using tracepoints I include "ruby/debug.h". This includes most of TracePoint's API but it seems like the C-equivalents for TracePoint#parameters, TracePoint#eval_script and TracePoint#instruction_sequence are missing/not being exported in the header.
**Background**
Most APIs like rb_tracearg_return_value are exported in "ruby/debug.h". If I understand correctly, the implementations for those methods are located in "ruby/vm_trace.c". The following methods implemented in "ruby/vm_trace.c" are missing in "ruby/debug.h":
* rb_tracearg_parameters
* rb_tracearg_eval_script
* rb_tracearg_instruction_sequence
**Proposal**
I propose to add those methods to "ruby/debug.h". From my limiting understanding the change should be simple and not break backward compatibility, because we'd only need to add those function declarations to "ruby/debug.h".
I'd be open to contribute this change if it was approved.
**Use cases**
I'm implementing a method call tracer for Ruby using the C-extension API. I wanted to get information about the parameters that the called method receives. When writing in Ruby this can be done using the TracePoint#parameters method, but I could not find the equivalent C-API. A workaround is to retrieve the method object (using the method_id) and check the method parameters.
**See also**
* Implementation of TracePoint#parameters in #14694
* Implementation of TracePoint#eval_script and TracePoint#instruction_sequence in #15287
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2024-09-20 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 14:38 richardboehme via ruby-core [this message]
2024-09-22 11:36 ` [ruby-core:119278] " richardboehme via ruby-core
2024-09-30 5:24 ` [ruby-core:119349] " mame (Yusuke Endoh) via ruby-core
2024-12-10 7:04 ` [ruby-core:120150] " ko1 (Koichi Sasada) via ruby-core
2025-01-11 20:51 ` [ruby-core:120614] " richardboehme via ruby-core
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-20757.20240920143834.53944@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).