导入zbar导致python以退出代码139退出 - 这可能导致在运行10.9的mac上出现这种情况？ [英] Importing zbar causes python to exit with exit code 139 - what could cause this on a mac running 10.9?
问题描述
我正在尝试在我的opencv工作流程中进行二维码识别，但程序会立即以代码139退出。
I am trying to get QR code recognition going in my opencv workflow but the program immediately exits with code 139.
import zbar 导致问题，因为当我删除它后，我的后续opencv代码执行。
import zbar causes the problem because when i delete it my subsequent opencv code executes.
我该如何诊断？它似乎是在/Library/Python/2.7/site-packages/中找到zbar python包（即没有声称包不存在），但随后它以代码139退出。任何想法是什么代码139？问题可能出在python绑定，zlib.h或其他地方吗？
How do I go about diagnosing this? It appears to be finding zbar python package in /Library/Python/2.7/site-packages/ (i.e. doesn't claim the package doesn't exist), but then it exits with code 139. Any idea what code 139 is? Is the problem likely in the python bindings, zlib.h, or someplace else?
python绑定包位于/Library/Python/2.7/site-packages/中：
The python bindings package is in /Library/Python/2.7/site-packages/:
zbar-0.10-py2.7.egg-info
zbar.so
推荐答案
致命错误由128 +错误代码表示。在您的情况下，这是128 + 11 = 139，其中11指的是SIGSEGV，即无效的内存访问。另请参阅：
Fatal errors are indicated by 128 + error code. In your case, this is 128 + 11 = 139, where 11 refers to SIGSEGV, i.e. invalid memory access. See also:
- http://www.linuxjournal.com/article/10844
- http://man7.org/linux/man-pages/man7/signal.7.html
如果您通过gdb，valgrind或Instruments运行代码，您可能能够找到发生这种情况的确切位置。
If you run your code through gdb, valgrind or Instruments, you may be able to find the exact location where this occurs.
这篇关于导入zbar导致python以退出代码139退出 - 这可能导致在运行10.9的mac上出现这种情况？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
