Skip to content

Don't check for stack overflow when ec is NULL #14236

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

Merged
merged 2 commits into from
Aug 15, 2025

Conversation

jhawthorn
Copy link
Member

If we hit a SEGV on a non-Ruby thread or during shutdown, previously this would usually cause another segfault. Avoiding this might allow for more useful error logs (elsewhere in the bug report we do check for ec missing)

This comment has been minimized.

Co-authored-by: Nobuyoshi Nakada <nobu.nakada@gmail.com>
@jhawthorn jhawthorn merged commit 0d0c051 into ruby:master Aug 15, 2025
85 checks passed
@jhawthorn jhawthorn deleted the segv_no_ec branch August 15, 2025 17:41
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.

2 participants