-
Notifications
You must be signed in to change notification settings - Fork 61
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
Segmentation Fault in Ruby 3.2 #171
Comments
Thanks for the info. I'm currently coaching 3 teams over the basketball season so I haven't had much time to spare. I haven't yet moved up the code and tests for Ruby 3 but that is next on my agenda. Also the CI I was using before switched domains and no longer provides free service for me so I need to move the test matrix over to Github Actions, or something as capable as the previous CI. Perhaps both. I understand your desire for this to be done quickly, but if no one else is picking this up at this time it'll have to wait until I'm free. |
@danielpclark perfectly understandable, no problem at all 👍 I might get someone on our side to put a PR together |
It appears that the memory layout of things has changed in Ruby 3.2; I just banged my head against it for #174. My commiserations to whoever has to chase down all the corner cases. |
any news about this? |
@EmmN , My main computer was down for 5 months (besides being busy coaching) and I got it up and running last week. I have an additional computer I'll be finishing building this week for AI related work. After that I'll likely get the CI test suite finalized with full Ruby 2 suite on Github Actions to be a 1 for 1 setup to as it was on Travis CI. Then I'll begin the Ruby 3 migration (Lord willing). That is the current update. |
@danielpclark Thanks! I believe that moving to rb-sys would be a good idea. |
Hey! Any updates on ruby 3 support? |
Hey @danielpclark ,
Hope you are doing well.
I've tried adding support for Ruby 3.2 for my project that is using Rutie and I'm now getting a SegFault (here's a PR that adds Ruby 3.2 as a target and you should be able to see logs from GH Actions for a full stack trace).
As far as I'm able to decipher it — the issue is that Rutie bindings for
Integer
useFixnum
class (when implementing theVerifiedObject
trait) which has been removed from Ruby 3.2. As a result the call to Rust crashes if it takes anInteger
as input.Hope it's a relatively quick fix.
The text was updated successfully, but these errors were encountered: