-
Notifications
You must be signed in to change notification settings - Fork 685
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
Resolve segfault issue #50
Comments
HI @tonywok : I thought I'd best add a segfault issue to this issue's thread rather than opening a new issue? I'm receiving a segfault when working through the I'm running Hope this helps! |
@mlk-kc Thank you! Yes, I'm still hopeful this is all the same root issue -- or at least caused from the same class of issue. Hoping to get some time to dive deeper in the coming days (been a bit heads down on work-work). Glad you found a work-around. |
No problem at all 😄 If I can provide any extra information, please let me know! |
I got past the segmentation fault by switching from 3.2.2 to 3.0.6. |
Thanks to @WarLockeR31 we found out that there is no segfault in Ruby 3.2.3. |
Duplicated by #45, #43, and I think #40
I'm able to reproduce this pretty reliably. Going to mark the above issues as duplicates. Let me know if for some reason you think they are distinct.
Seems to happen when I run
rake run
, but notrake
🤔. Will have to dig in when I get some time (hoping this week since I'm off work for a few days).The text was updated successfully, but these errors were encountered: