You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the tesseract.rb file just requires tesseract-ocr (line 25), and that require is what gets ffi involved.
If it's helpful:
tesseract-ocr gem info
$ gem list tesseract -d
tesseract-ocr (0.1.6)
Author: meh.
Homepage: http://github.com/meh/ruby-tesseract-ocr
License: BSD
Installed at: /Users/Mikayla/.rvm/gems/ruby-2.1.2
A wrapper library to the tesseract-ocr API.
ffi gem info
$ gem list ffi
ffi (1.9.6)
Author: Wayne Meissner
Homepage: http://wiki.github.com/ffi/ffi
License: BSD
Installed at: /Users/Mikayla/.rvm/gems/ruby-2.1.2
Ruby FFI
ffi-extra (0.1.0)
Author: meh.
Homepage: http://github.com/meh/ruby-ffi-extra
Installed at: /Users/Mikayla/.rvm/gems/ruby-2.1.2
Some extra methods for FFI
ffi-inline (0.0.4.3)
Author: meh.
Homepage: http://github.com/meh/ruby-ffi-inline
Installed at: /Users/Mikayla/.rvm/gems/ruby-2.1.2
Inline C/C++ in Ruby easily and cleanly.
Has anyone seen anything similar? I can take this to ffi, of course, but it seems unlikely that I'm the only one to have encountered this coming from tesseract.
I saw Issue 39, but that seems like a pretty different error message, and was also not resolved.
The text was updated successfully, but these errors were encountered:
I'm getting a segfault whenever I try to require tesseract. All I have in the file is
require 'tesseract'
and it crashes.The stack trace is here.
It looks like the
tesseract.rb
file just requirestesseract-ocr
(line 25), and that require is what gets ffi involved.If it's helpful:
tesseract-ocr gem info
ffi gem info
Has anyone seen anything similar? I can take this to ffi, of course, but it seems unlikely that I'm the only one to have encountered this coming from tesseract.
I saw Issue 39, but that seems like a pretty different error message, and was also not resolved.
The text was updated successfully, but these errors were encountered: