[ruby-core:120765] [Ruby master Feature#21086] Declare rb_profile_frames() family as async-signal-safe

Issue #21086 has been reported by osyoyu (Daisuke Aritomo). ---------------------------------------- Feature #21086: Declare rb_profile_frames() family as async-signal-safe https://bugs.ruby-lang.org/issues/21086 * Author: osyoyu (Daisuke Aritomo) * Status: Open ---------------------------------------- Since @ivoanjo 's change in https://github.com/ruby/ruby/pull/11036 , I believe `rb_profile_frames()` and `rb_profile_thread_frames()` could be marked as async-signal-safe. I remember @ko1 had a few reasons not to do so. I'd like to ask what @ko1 thinks now. -- https://bugs.ruby-lang.org/

Issue #21086 has been updated by osyoyu (Daisuke Aritomo). I've created a pull request: https://github.com/ruby/ruby/pull/12621 ---------------------------------------- Feature #21086: Declare rb_profile_frames() family as async-signal-safe https://bugs.ruby-lang.org/issues/21086#change-111630 * Author: osyoyu (Daisuke Aritomo) * Status: Open ---------------------------------------- Since @ivoanjo 's change in https://github.com/ruby/ruby/pull/11036 , I believe `rb_profile_frames()` and `rb_profile_thread_frames()` could be marked as async-signal-safe. I remember @ko1 had a few reasons not to do so. I'd like to ask what @ko1 thinks now. -- https://bugs.ruby-lang.org/
participants (1)
-
osyoyu (Daisuke Aritomo)