-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
Rails segmentation fault when no argument is passed #565
Comments
I'll look into it. It is just supposed to raise an exception like it does when not in rails although you are using a very old version of Ruby. |
I was not able to install ruby 2.3.3 on macOS. I'll try on a linux machine tomorrow. |
No success getting 2.3.3 installed. I did have 2.3.7 installed on an older machine I could use though. By itself, without rails there is no issue. I was not able to install an older version of rails. What confuses me is how the console would even be able to call a function with the wrong number of arguments. More recent versions of the rails console raises an exception before even calling Oj.dump with no arguments. I'm afraid there's not much else I can do since I can't install the versions you are running into issues with. If you are not able to upgrade you could test by trying to call another function that requires an argument with no arguments and see if the console has the same issue. |
Ok, thanks anyway! Btw, I tested this on some other functions requiring arguments, but I have the "wrong number of arguments" message. |
Can this be closed? |
yep |
Rails 4.2.7.1, Ruby 2.3.3
When I type
Oj.dump()
without any parameter on a Rails console, the server segfaults.The text was updated successfully, but these errors were encountered: