[#120465] [Ruby master Bug#20998] rb_str_locktmp() changes flags of frozen strings and string literals — "Eregon (Benoit Daloze) via ruby-core" <ruby-core@...>
Issue #20998 has been reported by Eregon (Benoit Daloze).
17 messages
2025/01/03
[ruby-core:120614] [Ruby master Feature#20757] Make rb_tracearg_(parameters|eval_script|instruction_sequence) public C-API
From:
richardboehme via ruby-core <ruby-core@...>
Date:
2025-01-11 20:51:46 UTC
List:
ruby-core #120614
Issue #20757 has been updated by richardboehme (Richard B=F6hme). I've added the methods to debug.h and in my small test case it seemed to wo= rk without any problems. The PR is at https://github.com/ruby/ruby/pull/125= 53. Let me know if this is fine like this or if I should change anything! ---------------------------------------- Feature #20757: Make rb_tracearg_(parameters|eval_script|instruction_sequen= ce) public C-API https://bugs.ruby-lang.org/issues/20757#change-111443 * Author: richardboehme (Richard B=F6hme) * Status: Assigned * Assignee: ko1 (Koichi Sasada) ---------------------------------------- **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#instructi= on_sequence are missing/not being exported in the header. =20 **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 i= n "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 =20 **Proposal** I propose to add those methods to "ruby/debug.h". From my limiting understa= nding the change should be simple and not break backward compatibility, bec= ause 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 rece= ives. 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 retr= ieve the method object (using the method_id) and check the method parameter= s. =20 **See also** * Implementation of TracePoint#parameters in #14694=20 * Implementation of TracePoint#eval_script and TracePoint#instruction_seque= nce in #15287=20 --=20 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.rub= y-lang.org/