Closed igrep closed 9 years ago
BTW, though I couldn't reproduce this time, I found JSON.parse nil
also causes it on my office's CI server.
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).
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 found require 'ffi_yajl/json_gem'
also caused it.
I can reproduce the segfault in the most recent published version with no other gems loaded on ruby 2.1.2p95:
~$ gem install ffi-yajl && ruby -e "require 'ffi_yajl/json_gem'; JSON.parse(1)"
Fetching: ffi-yajl-1.1.0.gem (100%)
Building native extensions. This could take a while...
Successfully installed ffi-yajl-1.1.0
1 gem installed
/Users/brasic/.rvm/gems/ruby-2.1.2/gems/ffi-yajl-1.1.0/lib/ffi_yajl/parser.rb:63: [BUG] Segmentation fault at 0x00000000000003
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]
[clipped]
Let me know if you want the rest of the trace.
Then, the output: