Skip to content
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 during require 'tesseract' (issue with ffi?) #43

Open
mikaylathompson opened this issue Nov 4, 2014 · 2 comments
Open

Segfault during require 'tesseract' (issue with ffi?) #43

mikaylathompson opened this issue Nov 4, 2014 · 2 comments

Comments

@mikaylathompson
Copy link

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 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.

@meh
Copy link
Owner

meh commented Nov 4, 2014

#39 is surely a missing headers/libraries issue (for whatever reason I never got notifications about it, hence no responses).

This looks like a bug in FFI itself, if it were a segfault on tesseract side you would get it while using it instead of on require.

@kithokit
Copy link

Any new finding for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants