-
Notifications
You must be signed in to change notification settings - Fork 22
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
Segfault when executing JSON.parse 1
in rails console
#2
Comments
BTW, though I couldn't reproduce this time, I found |
you need to require 'ffi_yajl/json_gem' in order to get JSON.parse compatibility interface. i'm not sure how you're even getting a stacktrace out of ffi_yajl without doing that. i haven't tested at all with rails, though, and i know that yajl-ruby had issues trying to making the json-compat stuff work in rails, and suspect that this gem would need its own patch to be correctly supported in rails without relying on monkeypatching over the JSON monkeypatches (and if yajl-ruby is also monkeypatching at the same time things could get very exciting -- ffi-yajl and yajl-ruby don't like to both get loaded into the same process since the c-libraries will conflict all over the place). |
I found |
I can reproduce the segfault in the most recent published version with no other gems loaded on ruby 2.1.2p95:
Let me know if you want the rest of the trace. |
Then, the output:
The text was updated successfully, but these errors were encountered: