* [ruby-core:120765] [Ruby master Feature#21086] Declare rb_profile_frames() family as async-signal-safe
@ 2025-01-23 15:32 osyoyu (Daisuke Aritomo) via ruby-core
2025-01-23 15:33 ` [ruby-core:120766] " osyoyu (Daisuke Aritomo) via ruby-core
0 siblings, 1 reply; 2+ messages in thread
From: osyoyu (Daisuke Aritomo) via ruby-core @ 2025-01-23 15:32 UTC (permalink / raw)
To: ruby-core; +Cc: osyoyu (Daisuke Aritomo)
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/
______________________________________________
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/
^ permalink raw reply [flat|nested] 2+ messages in thread
* [ruby-core:120766] [Ruby master Feature#21086] Declare rb_profile_frames() family as async-signal-safe
2025-01-23 15:32 [ruby-core:120765] [Ruby master Feature#21086] Declare rb_profile_frames() family as async-signal-safe osyoyu (Daisuke Aritomo) via ruby-core
@ 2025-01-23 15:33 ` osyoyu (Daisuke Aritomo) via ruby-core
0 siblings, 0 replies; 2+ messages in thread
From: osyoyu (Daisuke Aritomo) via ruby-core @ 2025-01-23 15:33 UTC (permalink / raw)
To: ruby-core; +Cc: osyoyu (Daisuke Aritomo)
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/
______________________________________________
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/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-01-23 15:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-01-23 15:32 [ruby-core:120765] [Ruby master Feature#21086] Declare rb_profile_frames() family as async-signal-safe osyoyu (Daisuke Aritomo) via ruby-core
2025-01-23 15:33 ` [ruby-core:120766] " osyoyu (Daisuke Aritomo) via ruby-core
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).