dbgx / lldb.nvim

No longer maintained. Possible alternative: https://github.com/rcarriga/nvim-dap-ui
Other
262 stars 20 forks source link

importing lldb on Mac OSX dumps fatal error. #16

Closed d0u9 closed 8 years ago

d0u9 commented 8 years ago

Due to the new SIP mechanism of El capitan, I installed another python via homebrew. However, when I import the Xcode's lldb library, fatal error is reported.

critiqjo commented 8 years ago

I have very very little experience with a Mac (and zero with the latest version). So bear with me...

  1. Are you able to run lldb as a standalone application?
  2. Are you able to use lldb from XCode?
  3. Did you run xcode-select --install after the upgrade??
  4. Have you read this article?

If none of that works, please provide more details about the error, and also post the output of

>>> import lldb

from python2 console.

d0u9 commented 8 years ago

I tied separately two version python, one is shipped with Xcode, one is installed via homebrew. The pre-installed python works fine, however, the homebrew installed python dumps error.

So, I wonder that whether the lldb.nvim provides an option to select which python to be used.

critiqjo commented 8 years ago

lldb.nvim does not provide any such option, because it doesn't have any control over it. Neovim has a global option which can be pointed to the pre-installed python, like so:

let g:python_host_prog = '/path/to/python'

Be sure that you can import neovim from the pre-installed python, after having python-client installed.