Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require Ruby 3.2.1+ #43

Merged
merged 1 commit into from
Nov 23, 2023
Merged

Require Ruby 3.2.1+ #43

merged 1 commit into from
Nov 23, 2023

Conversation

casperisfine
Copy link
Contributor

3.2.0 has a bug that cause rb_profile_frames to not be async signal safe: ruby/ruby#7116

It has been backported in 3.2.1, so might as well prevent the installation of the gem.

Fix: #42

cc @m-zielinski, @jhawthorn

3.2.0 has a bug that cause `rb_profile_frames` to not be async signal safe: ruby/ruby#7116

It has been backported in 3.2.1, so might as well prevent the installation of the gem.

Fix: jhawthorn#42
@casperisfine
Copy link
Contributor Author

Also before 3.3.0, the same issue happens if YJIT is enabled.

And on 3.3.0, the same issue still happens if N:M threads are enabled (tmm1/stackprof#221)

@jhawthorn
Copy link
Owner

Sure! (though I don't think the 3.3.0 issue is the same)

@jhawthorn jhawthorn merged commit 598fc88 into jhawthorn:main Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Segfault on Thread
2 participants