From: "alanwu (Alan Wu) via ruby-core" Date: 2025-05-14T14:11:05+00:00 Subject: [ruby-core:122097] [Ruby Bug#21338] TracePoint Not Triggered for Kernel#block_given? Issue #21338 has been updated by alanwu (Alan Wu). Status changed from Open to Rejected It's a C method in 3.4, so you can listen for `:c_call`: ``` ruby -ve 'TracePoint.new(:c_call) { p _1 }.enable { block_given? }' ``` Wether something is a C or Ruby method is not something we guarantee to be stable, though, so it's not a bug now that a different event fires. ---------------------------------------- Bug #21338: TracePoint Not Triggered for Kernel#block_given? https://bugs.ruby-lang.org/issues/21338#change-113251 * Author: cfis (Charlie Savage) * Status: Rejected * ruby -v: ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- When updating ruby-prof for Ruby 3.4, various tests now fail because a method enter/leave tracepoint is not triggered for `Kernel#block_given?` For example: https://github.com/ruby-prof/ruby-prof/blob/master/test/line_number_test.rb#L184 In 3.3 a tracepoint was triggered but not in earlier Ruby versions. -- 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/