[#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:120766] [Ruby master Feature#21086] Declare rb_profile_frames() family as async-signal-safe
From:
"osyoyu (Daisuke Aritomo) via ruby-core" <ruby-core@...>
Date:
2025-01-23 15:33:51 UTC
List:
ruby-core #120766
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/